Ticket #1002 (closed defect: fixed)

Opened 1 year ago

Last modified 9 months ago

304 (not modified) must have no Content-Length

Reported by: mihai_preda@yahoo.com Assigned to: jan
Priority: normal Milestone: 1.4.17
Component: core Version: 1.4.13
Severity: normal Keywords:
Cc: Blocking:
Need Feedback: 0

Description

According to RFC 2616 (section 4.3), these responses MUST NOT include a message body: 1xx, 204, 304. This means they should not have a Content-Length. But lighttpd generates a "Content-Length: 0" for 304.

Attachments

Change History

03/13/2007 02:44:29 AM changed by yasheng@gmail.com

I found this too. This should better be fixed.

HTTP/1.x 304 Not Modified Date: Tue, 13 Mar 2007 02:40:06 GMT Server: Apache/1.3.33 (Debian GNU/Linux) PHP/4.3.10-16 mod_gzip/1.3.26.1a mod_fastcgi/2.4.2 Connection: close Etag: "1880b-6797-43da2e2b"

HTTP/1.x 304 Not Modified Content-Length: 0 Date: Tue, 13 Mar 2007 02:44:02 GMT Server: lighttpd/1.4.13

08/18/2007 10:40:33 AM changed by jan

  • status changed from new to closed.
  • resolution set to fixed.
  • blocking changed.
  • pending changed.
  • milestone set to 1.4.17.

fixed in [1946]

Add/Change #1002 (304 (not modified) must have no Content-Length)




Change Properties
Action