Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a Date header to 304 responses #410

Merged
merged 1 commit into from Aug 7, 2012
Merged

Add a Date header to 304 responses #410

merged 1 commit into from Aug 7, 2012

Conversation

jamesward
Copy link
Contributor

This change adds a Date header to 304 responses and fixes an issue with CloudFront getting stuck in a RefreshHit cycle after hitting the TTL.

More information about why the Date header is required on 304 responses can be found at:
http://stackoverflow.com/questions/1587667/should-http-304-not-modified-responses-contain-cache-control-headers

Also, since a Date header should always be returned (not just for requests that have a Last-Modified header) the Date header is now set when a 200 response is constructed.

The FunctionalSpec has been added to test for the Date header on a 304 response.

This change adds a Date header to 304 responses and fixes an issue with CloudFront getting stuck in a RefreshHit cycle after hitting the TTL.

More information about why the Date header is required on 304 responses can be found at:
http://stackoverflow.com/questions/1587667/should-http-304-not-modified-responses-contain-cache-control-headers

Also, since a Date header should always be returned (not just for requests that have a Last-Modified header) the Date header is now set when a 200 response is constructed.

The FunctionalSpec has been added to test for the Date header on a 304 response.
pk11 pushed a commit that referenced this pull request Aug 7, 2012
@pk11 pk11 merged commit 5061b89 into playframework:2.0.x Aug 7, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants