Fix base64 encoded prefix received on the server side for chinese characters #1126
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
…racters Signed-off-by: Daniel Valdivia <[email protected]>
bexsoft
approved these changes
Oct 19, 2021
adfost
approved these changes
Oct 19, 2021
Alevsk
suggested changes
Oct 19, 2021
Contributor
Alevsk
left a comment
Alevsk
left a comment
There was a problem hiding this comment.
Testing a couple more use cases
Alevsk
approved these changes
Oct 19, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
When there are chinese characeters in prefix like
美好的一天混音/豆豉.mp3it encodes to576O5aW955qE5LiA5aSp5re36Z+zL+ixhuixiS5tcDM=but upong sending this to the server via rest, the+is received as spaceSigned-off-by: Daniel Valdivia [email protected]