-
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
Cannot copy blob from implicit root container #86
Milestone
Comments
We should have unit test for scenario like this. |
joostdenijs
pushed a commit
to joostdenijs/azure-sdk-for-java
that referenced
this issue
Jan 18, 2013
A couple of bug fixes
joostdenijs
pushed a commit
to joostdenijs/azure-sdk-for-java
that referenced
this issue
Jan 18, 2013
no Eclipse warnings for new code.
no longer in scope |
jianghaolu
pushed a commit
to jianghaolu/azure-sdk-for-java
that referenced
this issue
Apr 5, 2017
A couple of bug fixes
jianghaolu
pushed a commit
to jianghaolu/azure-sdk-for-java
that referenced
this issue
Apr 5, 2017
no Eclipse warnings for new code.
g2vinay
pushed a commit
to g2vinay/azure-sdk-for-java
that referenced
this issue
Mar 4, 2019
Java Storage Client Library 4.1.0
g2vinay
pushed a commit
to g2vinay/azure-sdk-for-java
that referenced
this issue
Mar 4, 2019
Updating versions for 5.5.0 release
navalev
pushed a commit
to navalev/azure-sdk-for-java
that referenced
this issue
Dec 24, 2019
Adding Suggest UTs
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Most of the blob APIs allow the the user to pass the empty string as the container name to indicate the implicit root container (as opposed to being explicit, using "$root").
However, that does not work for the source container's name when using the
copyBlob
API. Looking at the headers sent out, the problems is that the source is malformed with a double slash in the middle:The problem in in
BlobRestProxy.getCopyBlobSourceName
, where source container is checked for null, but not empty. The fix is to change:The text was updated successfully, but these errors were encountered: