GitHub user zwoop opened a pull request:
https://github.com/apache/trafficserver/pull/749
TS-4506 Should not remove Expires/Last-Modifed on 304 response
When generating a 304 page, we used to remove Expires and Last-Modified
always. This change makes sure we never touch Expires, and only remove
the Last-Modified header if the is an ETag in the response. This is per
the specs in
https://tools.ietf.org/html/rfc7232#page-18
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zwoop/trafficserver TS-4506
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/trafficserver/pull/749.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #749
----
commit fb4f565f4437f9a18d6e8b049cbd45586e83b543
Author: Leif Hedstrom <zw...@apache.org>
Date: 2016-06-03T21:35:30Z
TS-4506 Should not remove Expires/Last-Modifed on 304 response
When generating a 304 page, we used to remove Expires and Last-Modified
always. This change makes sure we never touch Expires, and only remove
the Last-Modified header if the is an ETag in the response. This is per
the specs in
https://tools.ietf.org/html/rfc7232#page-18
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
