Closed
Bug 39973
Opened 24 years ago
Closed 24 years ago
following link which includes a port ignores the port
Categories
(Core :: Networking, defect, P3)
Tracking
()
Future
People
(Reporter: josh-m, Assigned: gagan)
References
()
Details
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; m16) Gecko/20000520 BuildID: 2000052008 If you go to www.mirafiori.com and click on the "forum" image, it should go to http://www.mirafiori.com:8080/forumdemo/. It appears to send me to http: //www.mirafiori.com/forumdemo/ instead. Typing the URL in manually does seem to work- this only appears to affect following a link. Reproducible: Always Steps to Reproduce: 1. go to http://www.mirafiori.com/ 2. click on the "Forum" image. 3. note the error page. 4. now try typing in www.mirafiori.com:8080/forumdemo/ manually. That should work.
Updated•24 years ago
|
Component: Browser-General → Networking
Comment 1•24 years ago
|
||
WORKSFORME, Linux 2000-05-20-08. Windows only? This is a bad test case, as it goes through a cgi redirect. Lets try this one instead: <a href="http://www.mirafiori.com:8080/forumdemo/">http://www.mirafiori.com:8080/forumdemo/</a>
Reporter | ||
Comment 2•24 years ago
|
||
Nope, that doesn't cause the problem. I also tried saving the contents of http: //www.mirafiori.com/ to a file and clicking on the link from there. I still have the problem when I go to the real www.mirafiori.com page, though. It's 100% reproducable when i go to that page and click on that link.
Comment 4•24 years ago
|
||
This is definitly working on linux with latest builds. Anybody around who can confirm this for windows? There is no platform specific code I remember which could cause this.
2000060320 i'm marking as invalid, someone mentioned cgi, i don't see it. In the future it might be helpful to attach the source code of the page so that we can see how it looked then. view-info in nc4.73 says Last Modified: Sunday, May 28, 2000 11:49:32 PM Local time. Assuming that's to be believed the page i see now is not the same as the one from the bug. josh-m@hitchhiker.org please test with a newer build; thank you.
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
Reporter | ||
Comment 6•24 years ago
|
||
I've upgraded to a newer build (Win32 2000060415), and am still experiencing the same problem. I've reduced it to the test case at http: //www.hitchhiker.org/misc/bug.html. It seems very delicate- if I change anything (for example removing one of the links) it starts working properly. This is pretty strange stuff.
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
Comment 7•24 years ago
|
||
Okay, sometimes I now see this too with the current linux build on the testcase. But not always, only sometimes. This maybe the same problem as some other bugs dealing with mozilla not going to the right host or remembering the previous one. Confirming bug.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 8•24 years ago
|
||
I always see this bug when doing the following (PC/Linux, build 2000060508): \rm -rf ~/.mozilla mozilla http://www.hitchhiker.org/misc/bug.html ... and then clicking on the "Click Here" link. However I can't reproduce this problem when saving the "bug.html" page to a local file and running "mozilla file:///..." instead of "mozilla http://...".
Comment 9•24 years ago
|
||
The bug doesn't even occur if I replace www.hitchhiker.org with its IP address in the "mozilla http://..." step above. Seems it's a good precondition for the bug that the link points to a page on the host where the current page was loaded from.
Assignee | ||
Comment 10•24 years ago
|
||
should be fixed with bug 42841
Status: NEW → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → FIXED
Comment 11•24 years ago
|
||
This bug is still alive on PC/Linux, build 2000062610. Reopening. Bug 43713 may be related, but I'd suggest not to mark them dups until there is a fix for both.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 12•24 years ago
|
||
For an interesting test, check out: http://dormcam.mine.nu:8080/moztest.html The image on that page has a port specified (1234). Sometimes it goes to port 1234 (blue picture), sometimes it goes to port 8080 (red picture). Re-loading the page and also clearing the cache can have an effect on which picture you see. It should *always* be a blue picture.
Reporter | ||
Comment 13•24 years ago
|
||
I've just tested it with M18 on win32, using the URL mentioned (http://www.hitchhiker.org/misc/bug.html) and it still has the same behavior. Clicking on "click here" should give a connection refused error, but gives a not found error instead.
Comment 14•24 years ago
|
||
*** This bug has been marked as a duplicate of 51237 ***
Status: REOPENED → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•