Last-Modified header suppressed in 1.4.15
After upgrading to lighttpd 1.4.15 I no longer get the Last-Modified header returned when making a HEAD request.
This is an example of what is returned from a HEAD request now:
HTTP/1.1 200 OK Date: Fri, 15 Jun 2007 04:22:04 GMT Server: lighttpd/1.4.15 Content-Type: application/octet-stream Accept-Ranges: bytes Content-Length: 1531 Connection: close
#2 Updated by Anonymous over 9 years ago
Do you have a reference that describes the "problem" with Firefox's caching?
I'd rather have the ability to enable or disable this behavior in the configuration file.
The resources I'm delivering in which the Last-Modified header is important never change their content-type -- specifically they are jars delivered as static files.
#4 Updated by darix over 9 years ago
Yes this is a workaround for a bug in Firefox.
We have to often seen users bugged by firefox caching too much, and once they cleared the cache and restarted the browser, their changes suddenly "took effect".
Thats why we have in the #lighttpd topic: "Use curl for testing. Firefox caches too much."
#5 Updated by Anonymous almost 9 years ago
You wrote that Last-Modified is removed if no Content-Type is set, but I can see the Content-Type header in your posting as well as on my server responses.
We're having issues here with Squid not wanting to cache files if no Last-Modified or ETag header is present. What is the easiest way to get the get the Last-Modified header back for static files, without having to use an additional module like mod_setenv?
Also available in: Atom