34913 - 302 Redirects without content don't work.

Status: VERIFIED DUPLICATE of bug 22886

(SeaMonkey :: General, defect, P3)

Description

[Chris Purdum]

I was attempting to access some CompuServe sites
including the link above. This link does several
redirects, and after sniffing the network traffic,
I discovered it just stops after receiving a 302
that ended in the Location: header and had no
body. Here is a 302 that didn't work:

HTTP/1.1 302 Moved Temporarily
Server: Microsoft-IIS/4.0
Date: Wed, 05 Apr 2000 18:57:11 GMT
Location:
http://forums.beta.compuserve.com/login/default.asp?OrigUrl=http%3A%2F%2Fforums.beta.compuserve.com%2Fvlforums%2Fdefult.asp%3FSRV%3DOnlineIssues&RefUrl=

This happens in both Mozilla M14 and Netscape 6.  I have more network traces if
needed.

Comment 1

[Alan S. Jones]

This looks like a dupe 24884, both are 302 redirect errors "HTTP/1.0 302 
Redirect"

When 24884 is fixed someone should verify this.


*** This bug has been marked as a duplicate of 24884 ***

Comment 2

[Sean Richardson]

It seems doubtful that this is a DUP of bug 24884, "Mozilla caught in some loop 
when HTTP server redirects to itself" - there is no sign of a loop here,
but trying this with NN 4.72, the redirect goes to a secure (https:) page.
CC-ing [e-mail], who is familiar with both issues.

Comment 3

[Chris Purdum]

I agree with [e-mail] about it not being a loop.  There's no sign that
the browser has looped, it just gives a blank page and does nothing.  A
clarification though, the redirect that appears to be stopping the request is to
a non-SSL page.  That page, if you could get there, will redirect to an SSL site.

Another thing of note, the redirect is back to the same site, but with a fully
qualified URL.

Comment 4

[John Morrison]

Say [e-mail] ... is that 'Location: http://...' header followed 
by CR LF ? If so (missing CRLF), then that would be bug #22886. (I'll look
more later anyways, but I have to step out right now).

Comment 5

[John Morrison]

Oh ... and it's not a dup of 24884

Comment 6

[Chris Purdum]

I just confirmed from my network traces that there is indeed just one CRLF after
the Location: header in the 302 response from the server.  So it does appear to
be similar to bug #22886.  Is this going to be "fixed" so mozilla handles the
bad response?

Comment 7

[John Morrison]

I think then that this is a duplicate of bug #22886. It is an open bug, and is 
slated to be fixed M18. Thanks for following up, Chris.

*** This bug has been marked as a duplicate of 22886 ***

Comment 8

[Chris Purdum]

One final comment/question to satisfy my boss:  Does the fact that this is 
slated to go into M18 mean that it will make it into a Netscape 6 build/release 
at some point?

Comment 9

[Sean Richardson]

Yes, it's almost certain that this will get fixed by the time the .0 version
ships; if you want to know exactly when, add youself to the Cc: list for 
bug 22886. VERIFYing.