Lighttpd

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.

Otherwise FF will not detect the changed Content-Type.

Isn't that a server-side bug?
Are you allowed to change the content-type header without bumping the last modified header?

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."

Hi,
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?

add this last in your mimetype.assign and you will generate Last-Modified again.

1. make the default mime type application/octet-stream.
   "" => "application/octet-stream"

make the default mime type

That's not a good thing to do. If the web server doesn't know, it shouldn't make one up.

Is Firefox still buggy? It would be nice if this issue could finally be fixed.