https://redmine.lighttpd.net/https://redmine.lighttpd.net/favicon.ico?13667327412007-06-15T14:51:52Zlighty labsLighttpd - Bug #1236: Last-Modified header suppressed in 1.4.15https://redmine.lighttpd.net/issues/1236?journal_id=29752007-06-15T14:51:52Zjan
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Fixed</i></li><li><strong>Resolution</strong> set to <i>wontfix</i></li></ul><p>this is a "feature". If there is no content-type set, we remove the Last-Modified header to protect the user from firefoxs caching. Otherwise FF will not detect the changed Content-Type.</p> Lighttpd - Bug #1236: Last-Modified header suppressed in 1.4.15https://redmine.lighttpd.net/issues/1236?journal_id=29762007-06-17T22:42:27ZAnonymous
<ul></ul><p>Do you have a reference that describes the "problem" with Firefox's caching?</p>
<p>I'd rather have the ability to enable or disable this behavior in the configuration file.</p>
<p>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.</p> Lighttpd - Bug #1236: Last-Modified header suppressed in 1.4.15https://redmine.lighttpd.net/issues/1236?journal_id=29772007-07-02T15:15:21Zadmin
<ul></ul><blockquote>
<p>Otherwise FF will not detect the changed Content-Type.</p>
</blockquote>
<p>Isn't that a server-side bug?<br />Are you allowed to change the content-type header without bumping the last modified header?</p> Lighttpd - Bug #1236: Last-Modified header suppressed in 1.4.15https://redmine.lighttpd.net/issues/1236?journal_id=29782007-07-02T15:18:32Zdarix
<ul></ul><p>Yes this is a workaround for a bug in Firefox.<br />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".</p>
<p>Thats why we have in the #lighttpd topic: "Use curl for testing. Firefox caches too much."</p> Lighttpd - Bug #1236: Last-Modified header suppressed in 1.4.15https://redmine.lighttpd.net/issues/1236?journal_id=29792007-11-19T14:27:45ZAnonymous
<ul></ul><p>Hi,<br />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. <br />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?</p> Lighttpd - Bug #1236: Last-Modified header suppressed in 1.4.15https://redmine.lighttpd.net/issues/1236?journal_id=29802008-04-08T14:10:53ZAnonymous
<ul></ul><p>add this last in your mimetype.assign and you will generate Last-Modified again.</p>
<ol>
<li>make the default mime type application/octet-stream.<br /> "" => "application/octet-stream"</li>
</ol> Lighttpd - Bug #1236: Last-Modified header suppressed in 1.4.15https://redmine.lighttpd.net/issues/1236?journal_id=29812008-04-08T14:55:29Zadmin
<ul></ul><blockquote>
<p>make the default mime type</p>
</blockquote>
<p>That's not a good thing to do. If the web server doesn't know, it shouldn't make one up.</p> Lighttpd - Bug #1236: Last-Modified header suppressed in 1.4.15https://redmine.lighttpd.net/issues/1236?journal_id=48272008-10-10T19:05:03Zstbuehler
<ul><li><strong>Status</strong> changed from <i>Fixed</i> to <i>Wontfix</i></li></ul> Lighttpd - Bug #1236: Last-Modified header suppressed in 1.4.15https://redmine.lighttpd.net/issues/1236?journal_id=78472012-04-17T08:05:04Zpabs
<ul></ul><p>Is Firefox still buggy? It would be nice if this issue could finally be fixed.</p> Lighttpd - Bug #1236: Last-Modified header suppressed in 1.4.15https://redmine.lighttpd.net/issues/1236?journal_id=78492012-04-17T14:47:23Zdarix
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/7849/diff?detail_id=6054">diff</a>)</li><li><strong>Missing in 1.5.x</strong> set to <i>No</i></li></ul><p>there is no issue. configure proper mime types and you are fine.</p>