Closed Bug 272857 Opened 20 years ago Closed 18 years ago

"no-store" directives in META HTTP-EQUIV tags is ignored

Categories

(Core :: Networking: HTTP, defect)

Product:
Core
Component:
Networking: HTTP
Platform:
x86
Windows 2000
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 202896
Milestone:
mozilla1.9alpha1

People

(Reporter: mikus, Assigned: darin.moz)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

A webpage which contains cache-control directives is shown from cache instead of
being reloaded. Directives used are:

<head>
  <meta http-equiv="Cache-Control" content="no-store,no-cache,max-age=-1">
  <meta http-equiv="Pragma" content="no-cache">
  <meta http-equiv="Pragma" content="no-store">
  <meta http-equiv="Expires" content="-1">
</head>

The letter case of tags, directive names or values do not seem to have any
affect on behaviour. On the positive side, Firefox reloads a page if "no-store"
is returned in HTTP response header.

AFAIK, browsers are not required to process http-equiv tags, but many developers
rely on this behaviour. MSIE understands them, including cache-control tags.
MSIE 5.5 had a bug, the result of which was actual caching of the page, not
intended to be cached. I found about it here:
http://www.htmlgoodies.com/beyond/nocache.html, apparently MSDN should more
formal description.

On another note, I used two header tags on my page just like the author of the
article (see link above) suggests, and Firefox shows two sets of directives in
its Page Info/General/Meta table. Is this a bug? The directives have the same
name, why two sets of them?

Reproducible: Always
Steps to Reproduce:
1. Put aforementioned tags on a page and load it.
2. Leave the page.
3. Return to the page using Back button, the page is not reloaded.

Actual Results:  
Page is shown from cache

Expected Results:  
Page should be reloaded from server
Status: UNCONFIRMED → NEW
Ever confirmed: true
*** Bug 314422 has been marked as a duplicate of this bug. ***
It doesn't work, either, if no-cache is specified in HTTP header.
Target Milestone: --- → mozilla1.9alpha

*** This bug has been marked as a duplicate of 202896 ***
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.