Ticket #1236 (closed defect: wontfix)

Opened 1 year ago

Last modified 3 months ago

Last-Modified header suppressed in 1.4.15

Reported by: stepheneb Assigned to: jan
Priority: highest Milestone: 1.4.16
Component: core Version: 1.4.15
Severity: normal Keywords:
Cc: Blocking:
Need Feedback: 0

Description

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

Attachments

Change History

06/15/2007 02:51:52 PM changed by jan

  • status changed from new to closed.
  • resolution set to wontfix.

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.

06/17/2007 10:42:27 PM changed by anonymous

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.

07/02/2007 03:15:21 PM changed by Olaf van der Spek

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?

07/02/2007 03:18:32 PM changed by darix

  • pending changed.

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

11/19/2007 02:27:45 PM changed by anonymous

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?

04/08/2008 02:10:53 PM changed by anonymous

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

# make the default mime type application/octet-stream.

"" => "application/octet-stream"

04/08/2008 02:55:29 PM changed by Olaf van der Spek

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.

Add/Change #1236 (Last-Modified header suppressed in 1.4.15)




Change Properties
Action