Closed Bug 56523 Opened 24 years ago Closed 24 years ago

Redirection error when clicking on a URL

Categories

(Core :: Networking: HTTP, defect, P3)

DEC
Linux
defect

Tracking

()

VERIFIED DUPLICATE of bug 44153
mozilla0.8

People

(Reporter: jt.marsh, Assigned: darin.moz)

References

()

Details

On the starbulletin web page, there is a URL to
http://starbulletin.com/database/breaking. When you click this link, you end up
with ..dist/bin/chrome/packages/core/redirect_loop.xul. Often times clicking the
back button gets you to the proper page.
*** Bug 56524 has been marked as a duplicate of this bug. ***
Seems to be a problem with proxy servers and redirections -- specifically in
nsHTTPChannel::Redirect in nsHTTPChannel.cpp. The http status code is checked
for a 305 result and then does the proxy stuff. This does not seem right, plus
newURI does not seem to be set corrrectly when using a proxy.
*** Bug 56526 has been marked as a duplicate of this bug. ***
what buildid are you using?
I used the m18 src and compiled on an alpha running RH 6.2.

updating component and setting defualt owner.
Assignee: asa → gagan
Component: Browser-General → Networking
QA Contact: doronr → tever
The same happened here in 2000102808 Mac Trunk.
At http://www.cross-pcg.com/cross/
There is a link at the top :
http://www.cross-pcg.com/cross/home.asp
If you click this, the location window shows :
file:///...foo/chrome/packages/core/redirect_loop.xul
,where "...foo" is the folder Mozilla is located.
The URL I submitted may not reproduce the bug in other network settings,
because, here the starbulletin URL gets correctly redirected to the actual page
without any trouble.  Anyways, the cross-pcg URl is very reproducible here.
In today's build, the URL I posted does not bring Mozilla to redirect_loop.xul
 any more. 2000110208 MTrunk for MacOS.
Either Mozilla is fixed or the URL has been modified.  Another Missing bug?
jt.marsh@excite.com, are you still seeing this in current builds?
I think that this may be a dup of bug 58658. Reporter, does that look like what
you used to see at this page?
Other than ending up at the same place, I don't think this is similar to bug 58658.

Using 11/6 sources, I still have the same problem, but if I switch to a
different proxy server, the problem seems to go away. Previously I was not able
to use this proxy because m18 crashed on me when logging in to this
authenticating proxy server. 
 I looked at this with Lynx and with direct connections to the HTTP servers
involved. In lynx (even accepting cookies) and certainly using basic HTTP by
hand, it seems to wind up in an endless loop where one requests the URL
http://www.cross.com/home.asp? and is redirected to the same URL with a
'302 Object moved' response.
setting bug status to New
Status: UNCONFIRMED → NEW
Ever confirmed: true
Blocks: 61693
This bug also occurs on www.sprintpcs.com using the store locator, selecting a
state and pressing the find button.
I have seen this happen on almost any web page. I'm behind a FW-1 firewall and
get the redirect_loop.xul message in about 10% of links I click. Returning to
the previous page and clicking the link again usually gives the
redirect_loop.xul message again several times, but usually the third to fifth
time I get through to the link.

Oddly enoug, I have noticed a similar effect in NS4.x (all up to 4.76), but very
very rarely (maybe once in several hundred links). In NS4.76 the error message
provides a link to the actual page, so I don't need to push the back-button.

Sometimes, in Mozilla, when I push the back-button I get a redirect_loop.xul
error on the previous page as well. I'm running the latest nightly build
(2001010921) and have seen this error in all Mozilla versions (including NS6.0).
Target Milestone: --- → mozilla0.8
->me
Assignee: gagan → darin
Component: Networking → Networking: HTTP

*** This bug has been marked as a duplicate of 44153 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
verified dupe.
Status: RESOLVED → VERIFIED
QA Contact: tever → junruh
You need to log in before you can comment on or make changes to this bug.