Bug 868283

Summary: mod_cache regression in httpd 2.2.3-65: non-cacheable 304 responses serve bad data
Product: Red Hat Enterprise Linux 6 Reporter: Jan Kaluža <jkaluza>
Component: httpdAssignee: Luboš Uhliarik <luhliari>
Status: CLOSED ERRATA QA Contact: Zbysek MRAZ <zmraz>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.4CC: amarecek, ebenes, james, ksrot, roy
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: httpd-2.2.15-22.el6 Doc Type: Bug Fix
Doc Text:
Cause: An attempt is made to freshen a stale entry in the cache, and the 304 Not Modified response from the backend contains no ETag, no Last-Modified, and no Cache-Control header. Consequence: Because the 304 response from backend is uncacheable, httpd sends the cached response back, but without the original headers. This can lead to situation when for example Content-Type of cached response is not sent and therefore lost. Fix: Headers of cached original response are sent in the response. Result: httpd returns proper headers in this situation.
 Story Points: ---
Clone Of: 845532 Environment:
Last Closed: 2013-02-21 10:18:13 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 845532    
Bug Blocks:    

Comment 7 errata-xmlrpc 2013-02-21 10:18:13 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2013-0512.html