Project

General

Profile

Bug #1754

lighty SHOULD not include "Content-Encoding" in a 304 Not Modified response

Added by Anonymous almost 8 years ago. Updated almost 8 years ago.

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

0%

Missing in 1.5.x:

Description

According to RFC2616, a 304 Not Modified response SHOULD/MUST NOT include other entity-headers for a strong/weak cache validator request to prevent inconsistencies between cached entity-bodies and updated headers.

However, for a GET request w/ Accept-Encoding header, lighty w/ mod_compress includes Content-Encoding entity-header field within a 304 response. And this DOES confuse some proxy software, including squid, and client browsers about their cached objects.

Reference: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3.5

Simple patch file is attached.

-- yzlai

lighty_304.c.patch View - -- yzlai (613 Bytes) Anonymous, 2008-08-20 16:14


Related issues

Duplicated by Feature #1725: Turn off compression for 304 Fixed

Associated revisions

Revision 9e6ef84e (diff)
Added by stbuehler almost 8 years ago

Do not send content-encoding for 304 (#1754), thx yzlai

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

History

#1 Updated by stbuehler almost 8 years ago

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

Applied modified patch in r2296 (compare case insensitive).

Also available in: Atom