Project

General

Profile

Actions

Bug #1754

closed

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

Added by Anonymous about 16 years ago. Updated about 16 years ago.

Status:
Fixed
Priority:
Normal
Category:
mod_compress
Target version:
ASK QUESTIONS IN Forums:

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


Files

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

Related issues 1 (0 open1 closed)

Has duplicate Feature #1725: Turn off compression for 304FixedjanActions
Actions #1

Updated by stbuehler about 16 years ago

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

Applied modified patch in r2296 (compare case insensitive).

Actions

Also available in: Atom