Project

General

Profile

Bug #1002

304 (not modified) must have no Content-Length

Added by Anonymous about 12 years ago. Updated over 11 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
-
Category:
core
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Missing in 1.5.x:

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.

-- mihai_preda

Associated revisions

Revision 1946 (diff)
Added by jan over 11 years ago

don't send a Content-Length for 1xx, 204 and 304 (fixes #1002)

Revision 5bc539b6 (diff)
Added by jan over 11 years ago

don't send a Content-Length for 1xx, 204 and 304 (fixes #1002)

git-svn-id: svn://svn.lighttpd.net/lighttpd/branches/lighttpd-1.4.x@1946 152afb58-edef-0310-8abb-c4023f1b3aa9

History

#1

Updated by Anonymous about 12 years ago

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

-- yasheng

#2

Updated by jan over 11 years ago

  • Status changed from New to Fixed
  • Resolution set to fixed

fixed in r1946

Also available in: Atom