[4.x]: Fix static content sending 304 with entity. #8599
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
This was caused by error handling of HttpException. Now we honor headers in the exception, and we do not send entity if the status is one of the forbidden ones. Also fixed client, as 304 is not a real redirect, so it cannot have `Location`
oracle-contributor-agreement
bot
added
the
OCA Verified
romain-grecourt
previously approved these changes
Apr 2, 2024
romain-grecourt
approved these changes
Apr 2, 2024
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.
This was caused by error handling of HttpException. Now we honor headers in the exception, and we do not send entity if the status is one of the forbidden ones.
Also fixed client, as 304 is not a real redirect, so it cannot have
LocationDescription
Resolves #8543