Red Hat Bugzilla – Bug 113929
mod_expires headers not set when used in conjunction with mod_proxy
Last modified: 2014-06-27 05:07:53 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5)
Description of problem:
When using mod_proxy, the http headers sent to the client does not
countains the headers that are supposed to be set with mod_expires.
This works with an apache 2.0.48 compiled from apache.org sources.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.install an local apache listening on port 8088
2.add the following configurations directive in the rpm based apache
listening on port 80:
ProxyPass / http://127.0.0.1:8088/
ProxyPassReverse / http://127.0.0.1:8088/
so that every uri requested are supposed to be proxyed from the apache
running on port 8088.
3. look at the header generated:
wget -S http://127.0.0.1/
Actual Results: no Expires headers set.
Expected Results: Expires header present in server answer:
10 Expires: Tue, 20 Jan 2004 10:59:30 GMT
Update packages which contain the fix for this mod_expires issue are
available for testing purposes from:
Thanks for the report.
I have been testing this patch, in our test environment, for over a
week now, with no detected problems, our test set up is a simple
reverse proxy which adds expires headers to requested content.
Thanks for the patch,
Thank you Gareth. We'll integrate this fix for future errata updates.
An errata has been issued which should help the problem described in this bug report.
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen
this bug report if the solution does not work for you.