Closed Bug 515012 Opened 11 years ago Closed 9 years ago

302 redirect is cached despite of no-store no-cache

Categories

(Firefox :: General, defect)

defect
Not set

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: sergei, Unassigned)

References

()

Details

(Whiteboard: [CLOSEME 2011-1-30])

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.4pre) Gecko/20090902 Ubuntu/9.04 (jaunty) Shiretoko/3.5.4pre
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.4pre) Gecko/20090902 Ubuntu/9.04 (jaunty) Shiretoko/3.5.4pre

Request first comes to 
http://public.iponweb.net/firefox_test.html

then it goes to http://public.iponweb.net/google.php which redirects to google.com

After hitting reload / shift + reload several times it stops sending requests to google.php on reload. This should not happen b/c google.php appends the following headers:

Cache-Control	no-cache, no-store, must-revalidate
Expires	Mon, 26 Jul 1997 05:00:00 GMT
Pragma	no-cache


Reproducible: Always

Steps to Reproduce:
1. go to http://public.iponweb.net/firefox_test.html, notice request coming go google.php
2. hit reload - request to google.php is cached
3. if it doesn't reproduce on step 2 hit shift + reload, then reload again.
Actual Results:  
Browser doesn't do request to google.php, it uses previously cached result

Expected Results:  
Browser should always send request to google.php first b/c of cache-control headers
I also tried adding different headers like max-age=0 and their combinations, they did not seem to help.

When google.php returns 200 OK with some content (say pointing to google too) it does not get cached. Seems like the problem only occurs for return codes 3XX
The title of this bug is a bit misleading.

The redirect isn't cached (open a new tab to the same URL and you'll see that you get the 302 again).

The complaint in this bug is really a request:

"When hitting refresh on a page that has an IFRAME, please reload that IFRAME from its *ORIGINAL* URL, not the URL that it's CURRENTLY showing."

I expect that such a change would break both sites and potentially the user's expectation that "Refresh" refreshes each subframe's *CURRENT* location.
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles

You can also try to reproduce in Firefox 4 Beta 8 or later, there are many improvements in the new version, http://www.mozilla.com/en-US/firefox/all-beta.html
Whiteboard: [CLOSEME 2011-1-30]
No reply, INCOMPLETE. Please retest with Firefox 3.6.13 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.