Closed Bug 277654 Opened 20 years ago Closed 20 years ago

application/x-httpd-php type refusing to refresh

Categories

(Firefox :: General, defect)

1.0 Branch
x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: redshodan, Assigned: bugzilla)

Details

Firefox will not try to see if the content of an URL has changed after it gets a file of type application/x-httpd-php. This type came from a badly configured web server (the type was defined, but the php engine was disabled). After removing the php file and replacing it with a normal .html, the URL would result in the index.html, instead of the index.php. This was verified with elinks. But firefox would bring up the Save As dialog for the index.php. The only way to clear it was to clear the cache.
The problem is this : Firefox asks the server if the document changed and apache reports that the document is still the old one (nothing changed(. -< invalid
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
I must disagree. When I revist the URL with firefox, the index.php that it had gotten before no longer exists on the apache server. I manualy removed it. Like I said, elinks got the index.html correctly. So it cant be that the document hasnt changed. It looks like firefox never looks again for this type of file (for whatever reason). You can quit and restart firefox and it will behave the same. The only way I've seen to fix it is clear the cache.
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
Firefox just asks the server if the document has changed. The usual Apache bug is that it still reports that nothing changed and Firefox will use the cached document. This is a bug in Apache and not Mozilla/Firefox. -> invalid You can reopen this bug if you are sure that the serer reports that the file changed and if you attach a http log (before and after) http://www.mozilla.org/projects/netlib/http/http-debugging.html
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago20 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.