Build ID:2000033116 I have a web app that uses redirects. This app is behind a proxy. When trying to access the app and a redirect is sent back to Mozilla, I recieve the error: HTTP/1.1 302 Moved Temporarily Server: Microsoft-IIS/4.0 Date: Wed, 05 Apr 2000 03:32:39 GMT Cache-Control: max-age=0 Connection: close Content-Type:text/html;charset="iso-8859-1" Set-Cookie:sesessionid=KTKAAQYAAAA4ODA4NWOAAAA;Path=/ Cache-Control:no-cache="set-cookie,set-cookie2" Expires:Thu, 01 Dec 1994 16:00:00 GMT Location:/b2bjava/login.jsp?invalidlogin=true Document moved This document has moved here. This error has happened in IE4, but has since been fixed in IE5. Here is the problem: HTTP1.1 will try to use keep-alive connections to a web server to minimize the number of connections to estabilsh to the server. However, this kinda falls apart when the request goes through a proxy. That's because the connection to the server will be closed, but the browser will try to get the next file through the open connection. This results in the 'Document has moved' response from the server (or it might be the HTTP protocol, i am not sure). In any case, I think the correct behavior is that Mozilla (or the networking lib) should detect this response and silently try to get the document via a new connection. How to reproduce: Go to b2b.panasonic.com enter aaa as username and aaa as password Submit This will result in the 'Document has moved'. This is a pretty bad handling of a redirect and this really irked alot of users of IE4 when this happened to us, and I hope we won't see this when Moz gets released! -Chris

I think it's cool that no one has commented on this yet.

knoll@eclipse.net - this WORKSFORME both in a browser from the time you reported and a current one. Has the page been changed? Does this problem still exist? Do you have another URL where we can see it? Gerv

Reporter said: "After the status was changed, (and it was a works-for-me) I went back to the exact same build and tried it again and it worked!!! Which is odd, because I copied and pasted the output header from the browser (I wouldn't go through all tha ttrouble to type all that otuput up 8)) Anyways, I am not sure if it's really fixed or soemthing different changed on the server I was hitting. I'll have to hit it via a proxy or something to test it again." Gerv

knoll@eclipse.net - have you had a chance to test this problem again with a proxy? Gerv

Marking WORKSFORME. Please ask for this bug to be reopened if you see this problem again. Gerv

verified wfm