Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1347648 - Apache can not cache content if Expires header is modified
Apache can not cache content if Expires header is modified
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: httpd (Show other bugs)
7.2
All Linux
urgent Severity high
: rc
: ---
Assigned To: Web Stack Team
Martin Frodl
: ZStream
Depends On: 1331341
Blocks:
  Show dependency treegraph
 
Reported: 2016-06-17 06:28 EDT by Marcel Kolaja
Modified: 2016-07-18 12:50 EDT (History)
6 users (show)

See Also:
Fixed In Version: httpd-2.4.6-40.el7_2.2
Doc Type: Bug Fix
Doc Text:
In a caching proxy configuration, the mod_cache module would treat content as stale if the Expires header changed when refreshing a cached response. As a consequence, an origin server returning content without a fixed Expires header would not be treated as cacheable. The mod_cache module has been fixed to ignore changes in the Expires header when refreshing content. As a result, such content is now cacheable, improving performance and reducing load at the origin server.
Story Points: ---
Clone Of: 1331341
Environment:
Last Closed: 2016-07-18 12:50:33 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:1422 normal SHIPPED_LIVE Important: httpd security and bug fix update 2016-07-18 16:50:15 EDT

  None (edit)
Description Marcel Kolaja 2016-06-17 06:28:37 EDT
This bug has been copied from bug #1331341 and has been proposed
to be backported to 7.2 z-stream (EUS).
Comment 9 errata-xmlrpc 2016-07-18 12:50:33 EDT
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.

https://access.redhat.com/errata/RHSA-2016:1422

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