This repository was archived by the owner on Jun 4, 2024. It is now read-only.
Handle UTF-8 encoding #32
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
|
Looks good. 💃 Can you add that case to |
|
💃 |
alexander-daniel
added a commit
that referenced
this pull request
Oct 26, 2015
Handle UTF-8 encoding
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.
Will Resolve: #15, #24, #26
So the issue is fixed on the backend API to handle UTF filenames.
I've made this change where we create a new
Bufferfrom the urlencoded string, and that fixes the count error forcontent-lengthwhere UTF8 chars count as 2.Feel free to give it a try:
https://gist.github.com/alexander-daniel/bc8021e8be3d157ad16a
@bpostlethwaite @etpinard