-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unicode issues in core/utils/pipeline/Base64StringAdapter.java #193
Milestone
Comments
joostdenijs
added a commit
to joostdenijs/azure-sdk-for-java
that referenced
this issue
Jan 18, 2013
CloudBlob Fix: Ensure Client side exceptions are not resumed
gcheng
pushed a commit
to gcheng/azure-sdk-for-java
that referenced
this issue
Mar 7, 2013
fix ready! |
Looks good. |
g2vinay
pushed a commit
to g2vinay/azure-sdk-for-java
that referenced
this issue
Mar 4, 2019
5.4.0 Release
sima-zhu
pushed a commit
to sima-zhu/azure-sdk-for-java
that referenced
this issue
Mar 21, 2019
* Rename classes in RestProxy, inline populateMatrix() function * Working on proxy details classes * Rearrange v2 RestProxy classes and add tests * Fix checkstyle errors * Pass checkstyle. Extract HttpClient and SerializerAdapter from RestClient for RestProxy * Updates based on pull request reviews
mssfang
pushed a commit
to mssfang/azure-sdk-for-java
that referenced
this issue
Apr 23, 2019
* Fixing a memory leak in qpid layer. When service force closes an idle connetion, it is not properly freed in qpid layer. Includes some minor changes to make code simpler. * Fixing a code review comment.
navalev
pushed a commit
to navalev/azure-sdk-for-java
that referenced
this issue
Dec 24, 2019
* Resolve checkstyle issues
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Dev estimate: 1
Test estimate: 0.5
The following code exists in
Base64StringAdapter
:The input for the constructor is a byte array. This is unpredictable because if no encoding is specified, the constructor uses the platform's default charset. For example, if someone sets their platform's default charset to UTF-16, even ASCII characters will be un-parseable.
In the context of the code, it appears that the data should be interpreted using UTF-8. If that is the case, then, it should be made explicit.
The text was updated successfully, but these errors were encountered: