271848 - Firefox forgets to write referer into html header when switching to https

Status: RESOLVED EXPIRED

(Core :: Networking: HTTP, defect)

Description

[Peter Vojnisek]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10

on a corporate webpage there are ssl pages. if I open a new browser and write
the https:// page in, it redirects me to an other page (also https), but that
page does not get any information about the referrer url. (it is used for a
login - to jump back to the right url after login or register). It is ok with IE
or Opera...

Reproducible: Always
Steps to Reproduce:
1. write in a https address
2. it will redirect you to an other https page to log in
3. the page gets the referer and stores it
4. you fill out the login form and post it
5. after post the page shoul redirect you you to the hpps page written in 1.
6. but (only with Firefox - IE and Opera are ok) the address is null!

Comment 1

[Matthias Versen [:Matti]]

Do you mean the security feature form bug 141641 ?

Comment 2

[Peter Vojnisek]

Now it looks that the problem exists (and only with firefox - moz 1.7.3, IE6 and
Opera are ok), but I am not sure about the case anymore... I have to discover it
more precisely, because it doesn't reproducable on every server configuration.

Comment 3

[Christian :Biesinger (don't email me, ping me on IRC)]

is this a <meta> refresh, or HTTP 302 Found?

Comment 4

[Peter Vojnisek]

It looks that everything is found but after the server changes from http to
https, firefox looses session. 
It is easy to test if you make a https page which redirect you to a login page
(you store the url of the https address in the session), you log in, and the
stored data changes to null - looks like loosing the session. when I change
cookies off it is ok...

Comment 5

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 6

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.