158034 - plain/text does not reload on page reload

Status: RESOLVED DUPLICATE of bug 198072

(Core :: Networking: Cache, defect)

Description

[Sean Proctor]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.1a+) Gecko/20020706
BuildID:    2002070608

Viewing a page, then changing it's content type requires clearing the disk cache
in order to update the content type in mozilla.

I've had this problem in galeon as well, so I don't think it's a new issue.

Reproducible: Didn't try
Steps to Reproduce:
1.  View web page
2.  Change content-type of that page on the server
3.  view page again

Actual Results:  web page maintains original content-type

Expected Results:  web page should get updated content-type

Comment 1

[Boris Zbarsky [:bzbarsky]]

Is that regular reload or shift-reload?  What is your "Compare to page on
network" setting in preferences set to?

Comment 2

[Sean Proctor]

this is weird to me.  shift-reload works.  whenever I'm working on my webpage
and I reload (normal reload) the page... I can see the changes.  why is that not
the case with text/plain documents?  why would I reload a text/plain document if
I expected the results from the server to be the same?  (it's not like there's a
script I'd like to restart, etc)

I have the setting set to "when the page is out of date"

Comment 3

[Sean Proctor]

ok, my original assumption was off.  basically when I reload a text/plain
document, it loads from the cache.  why would I want to reload a text/plain
document if I didn't want to refetch it from the server?

(I changed the summary to reflect this)

Comment 4

[gordon]

Reload doesn't treat text/plain documents differently.  Depending on your HTTP
cache validation preferences (Edit->Prefs->Advanced->Cache), HTTP may send an
If-Modified-Since requests to the server for the top level document.

A shift-reload always requests a new document from the server, and overwrites
any existing cache entry (on the browser and any proxy servers between the
client and the originating server).

If your HTTP cache validation preference is set to "Never" or "Once per
session", reload won't refetch the page.  If it's set to "When page is out of
date" and it hasn't expired, it won't be refetched either.  It will go through
layout again, and sometimes that's what users want.

Marking INVALID.  If this explanation doesn't seem to cover your situation,
please reopen the bug and we can continue to investigate the problem.  Thanks.

Comment 5

[benc]

If you had access to your log files, you would probably see a 304 response
because the server did send an updated response even though you made the change.

Comment 6

[benc]

This is the likely cause...

*** This bug has been marked as a duplicate of 198072 ***