Closed Bug 101393 Opened 24 years ago Closed 24 years ago

referrer value is null

Categories

(Core :: DOM: Navigation, defect)

x86
Windows NT
defect
Not set
major

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: drewruscil, Assigned: adamlock)

Details

From Bugzilla Helper: User-Agent: Mozilla/4.76 [en] (WinNT; U) BuildID: 9.4 when submitting from a form page which was DYNAMICALLY created with a servlet, the referrer value after a redirect from the action servlet is null. NB: if the form page was a static page, and the same servlet is called by the submit button to redirect, the referrer is correct (all pages on both servers are https) Reproducible: Always Steps to Reproduce: 1.create a static form page, and a servlet to service it with a redirect 2. note the referrer value when the destination URL is reached 3.use a servlet to dynamically create the form page in 1. above and then note tne null referrer value Actual Results: as described Expected Results: as described the first time ever any browser acted this way
Is the static page on the same server as the dynamic page in your test? We do not send referrer cross-domain on https pages for security reasons....
Comments from reporter: For both tests, static and dynamic, https pages resided on different servers. Strange as it seems to us, we found the distinguishing factor to be only the starting - whether it was a static form page, or a dynamically created form page. (?????) Also, never before has a referrer across https domains, or servers, not been sent. IE still does it, and Netscape did it up to 6.1. Is this a new direction inspired by a stricter interpretation of the spec?
i think we're just mostly broken, but i could be wrong. i also think this is already reportd, but i could be wrong. If you could supply a public testcase that'd be wonderful...
Assignee: asa → adamlock
Component: Browser-General → Embedding: Docshell
QA Contact: doronr → adamlock
Mitch, do you want to deal with this one?
This is not really my area. I suggest Necko or PSM.
Rick, do you have any ideas for this?
so, is the issue that the submit page was created via document.write(...)? i can believe that the referer could get 'lost' in a generated page :-)
Marking these all WORKSFORME sorry about lack of response but were very overloaded here. Only reopen the bug if you can reproduce with the following steps: 1) Download the latest nightly (or 0.9.6 which should be out RSN) 2) Create a new profile 3) test the bug again If it still occurs go ahead and reopen the bug. Again sorry about no response were quite overloaded here and understaffed.
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.