fix: Use weak etags instead of etag #9
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We are not conforming to strong etags anyway and they are dropped by cloudlare and nginx when response is compressed as it is not hash of final output response
pguyot
pushed a commit
to Thegreendata/flask-rest-jsonapi
that referenced
this pull request
May 12, 2021
We are not conforming to strong etags anyway and they are dropped by cloudlare and nginx when response is compressed as it is not hash of final output response
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We are not conforming to strong etags anyway and they are dropped
by cloudlare and nginx when response is compressed as it is not
hash of final output response