go to the above URL by pasting it into the location bar, then click on the "complete story" link below given here for convinience: http://www.idg.net/go.cgi?id=604534 mozilla tries to open the "go.cgi" page on the linuxtoday.com server which is completely wrong, resulting in a 404. This also happens (seemingly at randoml) with many other URLs, but it's 100% reproducible on my system with the URL's given below.
The link works just fine on a current CVS, linux. Which build ID are you testing? Are you using some kind of proxy?
Summary: Mozilla munges cross-site URL's resulting in 404's → Mozilla munges cross-site URL's resulting in 404's
Not a blocker. Reducing severity.
Severity: blocker → normal
A similar effect can be achieved by 1) start mozilla 2) enter "www.kerneltrap.com" in the location bar, press enter 3) press CTRL-t to open a new tab 4) enter "www.google.com" in the location bar, press enter Mozilla reloads the www.kerneltrap.com page in the new tab instead of opening www.google.com. Again, 100% reproducible and also very annoying ;-) Regards, Uwe
Can't reproduce that either. Again: Are you using some kind of proxy?
mea culpa... I disabled the junkbuster proxy on the local machine (direct connection to the internet), and everything works! I've been using the junkbuster for years, and as mentioned in the previous description this "bug" came up about six months ago. So is this a mozilla problem or a netscape problem? I would say mozilla because aother browsers work fine on the same machine, using the same proxy. Thanks for helping, uwe
It's a well known junkbuster problem, but there's a workaround in Mozilla: See release notes about proxies: http://www.mozilla.org/releases/mozilla0.9.6/#problems In short: Open prefs, in prefs, open Debug->Networking, and under HTTP Version: change 1.1 to 1.0. *** This bug has been marked as a duplicate of 38488 ***
Status: UNCONFIRMED → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → DUPLICATE
verified Junkbuster is broken with http/1.1 other Browser work because : NS4.7x can only HTTP1.0 IE use always Http1.0 with a proxy
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.