Closed Bug 114682 Opened 24 years ago Closed 24 years ago

Wrong URL when clicking on a link

Categories

(Core :: Networking: HTTP, defect)

x86
Linux
defect
Not set
major

Tracking

()

RESOLVED WORKSFORME
mozilla0.9.9

People

(Reporter: ghlenn, Assigned: darin.moz)

Details

From Bugzilla Helper: User-Agent: Mozilla/4.72C-GWillard [en] (X11; I; Linux 2.2.13 i586) BuildID: 2001121108 The current URL gets concatenated to the new URL and forms a URL that does not exist Reproducible: Always Steps to Reproduce: 1.http://css.nu/pointers/index.html 2.clicking http://style.cleverchimp.com/cssui/ 3.no go Actual Results: "Page not found on this server" with a URL http://css.nuhttp://style.cleverchimp.com/cssiu/ Expected Results: Gone to the link that was clicked When Preferences are set to Memory cache 4096 and Disk cache 50000 (default settings) this bug occur; however, when setting the Memory cahce to 0 (zero) and the Disk cache to 0 (zero) and the ccomparison of pages (net vs cached) to Never, the problem goes away
Reporter: are you using a proxy?
WFM, with cache settings as prescribed. Build ID: 2001 12 10 03. Windows 2000.
I get this same behavior. Currently using build ID 2001122106 on Windows NT 4.0 sp6 I am using a proxy server. HTTP proxy only, No Proxy For: is blank. Setting cache to 0,0,never as prescibed does cause the behavior to stop.
cache or proxy incompatabilty. over to Necko
Assignee: asa → gordon
Status: UNCONFIRMED → NEW
Component: Browser-General → Networking: Cache
Ever confirmed: true
QA Contact: doronr → tever
Target Milestone: --- → mozilla0.9.9
Darin, any ideas what could cause this bizarre URL munging?
Assignee: gordon → darin
Component: Networking: Cache → Networking: HTTP
could someone able to repro this bug please submit a HTTP log? here's how: 1) setenv NSPR_LOG_MODULES nsHttp:5 2) setenv NSPR_LOG_FILE http.log 3) cd /path/to/mozilla 4) ./mozilla 5) # repro bug 6) # add http.log as an attachment to this bug report doing so will help us determine what's going on here. thx!
william: please try a newer build. i just tested the 2002-01-29/09 linux build and cannot reproduce this problem. marking WORKSFORME. it's possible that the build you have tested had a bug that caused this problem.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.