Closed
Bug 199073
Opened 23 years ago
Closed 23 years ago
If only the Content-Type of a file changes, the cached headers are not updated.
Categories
(Core :: Networking: Cache, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 198072
People
(Reporter: bugzilla, Assigned: gordon)
Details
User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.3) Gecko/20030313
Build Identifier: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.3) Gecko/20030313
If the Content-Type of a URI is could change without changing the file itself.
In which case the Last-Modified etc., headers remain the same, and only
Content-Type changes. If Mozilla has a local copy of the file, it seems to use
it; however it fails to updated it's local information about the Content-Type.
For instance a text/html file could be changed to a text/plain file without
changing the file itself (or text/plain changed to text/html). In this case
Mozilla should rerender the local files as text/plain, but instead continues to
render it as text/html (or it should render the file as text/html, but instead
continues to render it as text/plain).
Reproducible: Always
Steps to Reproduce:
1.Create some HTML resource at some URI like http://www.example.com/foo
2.Serve that file as text/plain. With Apache you could add
<Files foo>
ForceType text/plain
</Files>
to a .htaccess file.
3.View the URI in Mozilla. It correctly appears as a plain text file. You can
see the HTML tags, etc.
4.Now serve the file as text/html. In Apache use ForceType text/html as above.
5.Reload the URI.
Actual Results:
The file is still rendered as text. You can see the HTML tags, etc.
Expected Results:
The file should have rendered as an HTML file since it is now served as text/html.
To workaround: change the last modified date on the server, or flush the memory
and disk cache on Mozilla.
This looks like a dup of bug 198072.
*** This bug has been marked as a duplicate of 198072 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Web admin should check their server logs before filing cache bugs.
Please look at the information in the other bug to see what is going on. If you
have a different problem, reopen, and provide some web log data.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•