This repository was archived by the owner on Dec 24, 2022. It is now read-only.
-
Couldn't load subscription status.
- Fork 623
Support uppercase file extentions #535
Merged
Merged
Conversation
This file contains hidden or 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
thx for the PR 👍 Can you also approve the Contributor License Agreement so we can merge this, thx.
I've approved the license agreement.
thx for the PR, this change is now available from the latest ServiceStack v5.11.1 that's now available on MyGet.
Great :)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I've noticed that uppercase extensions of binary files are treated as text. I've encountered that in the ServiceStack.Aws project.
The result was that files named like IMG_123**.JPG** were returning different content lengths when renamed to IMG_123**.jpg** (on S3)