Fix content type being reset when using file cache storage #2117
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
|
Hi, any news regarding this PR ? |
|
Looks good, thanks! |
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
There has been a longstanding issue in
SanitizedFile#move_towhere an existing content type would be lost. This was exacerbated by the changes in #1312, which made the file cache store usemove_toall the time.Prior to this fix, anyone using the file cache store will lose any explicitly set content type. This can be seen in: #1841.
This PR solves the underlying
SanitizedFileissue, and adds some specs to ensure the same issue isn't present in the fog storage.