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

Expose the ETag header in 304 responses. #404

Merged
merged 1 commit into from
Feb 3, 2016
Merged

Conversation

Natim
Copy link
Member

@Natim Natim commented Jan 29, 2016

Add a test to show the behavior in mozilla-services/cliquet#631

@leplatrem leplatrem changed the title Expose the ETag header in 304 responses. [WIP] Expose the ETag header in 304 responses. Jan 29, 2016
@leplatrem
Copy link
Contributor

@leplatrem leplatrem changed the title [WIP] Expose the ETag header in 304 responses. Expose the ETag header in 304 responses. Feb 1, 2016
@leplatrem
Copy link
Contributor

@almet r?

@almet
Copy link
Member

almet commented Feb 3, 2016

That looks good to me!

@almet
Copy link
Member

almet commented Feb 3, 2016

r+

almet added a commit that referenced this pull request Feb 3, 2016
Expose the ETag header in 304 responses.
@almet almet merged commit 6ed0036 into master Feb 3, 2016
@almet almet deleted the etag-not-exposed-in-304 branch February 3, 2016 08:55
@almet almet removed the in progress label Feb 3, 2016
@@ -120,7 +120,8 @@ def default_bucket(request):
try:
response = request.invoke_subrequest(subrequest)
except httpexceptions.HTTPException as error:
if error.content_type == 'application/json':
is_redirect = error.status_code < 400
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would have tested 304 only there.

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.

3 participants