Bug 868283 – mod_cache regression in httpd 2.2.3-65: non-cacheable 304 responses serve bad data

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 868283 - mod_cache regression in httpd 2.2.3-65: non-cacheable 304 responses serve bad data

Summary:	mod_cache regression in httpd 2.2.3-65: non-cacheable 304 responses serve bad...

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 6
Classification:	Red Hat
Component:	httpd (Show other bugs)
Sub Component:
Version:	6.4
Hardware:	All Linux

Priority	unspecified Severity high
Target Milestone:	rc
Target Release:	---
Assigned To:	Web Stack Team
QA Contact:	Zbysek MRAZ
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:	845532
Blocks:
	Show dependency tree / graph

Reported:	2012-10-19 08:13 EDT by Jan Kaluža
Modified:	2013-07-03 09:17 EDT (History)
CC List:	5 users (show)

See Also:
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 05:18:13 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2013:0512	normal	SHIPPED_LIVE	Low: httpd security, bug fix, and enhancement update	2013-02-20 16:29:30 EST

Groups: None (edit)

Comment 7 errata-xmlrpc 2013-02-21 05:18:13 EST

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

Note You need to log in before you can comment on or make changes to this bug.