Need to properly handle null for blob container names about azure-sdk-for-java HOT 9 CLOSED

I think this should be fixed with unit test(s). root container is an important scenario to support.

from azure-sdk-for-java.

null value should go to root (same as empty string)

from azure-sdk-for-java.

It depends on the method, for create container, it doesn't make sense to send the create container request because the root container is already there.

from azure-sdk-for-java.

I think that null should be the root container everywhere, and in the case of create container, the request to create the root container will fail server side.

from azure-sdk-for-java.

also for delete container, if we do not curb the request on client side, an incorrect delete container may delete the whole account in future.

from azure-sdk-for-java.

fix ready.

from azure-sdk-for-java.

actually, no, it is more complicated than it looks like.

http://msdn.microsoft.com/en-us/library/windowsazure/ee395424.aspx

from azure-sdk-for-java.

To list the blobs in the root container:
GET http://myaccount.blob.core.windows.net/$root?restype=container&comp=list

To delete the root container:
DELETE http://myaccount.blob.core.windows.net/$root?restype=container

Missed from documentation, I guess creating a root container should be

PUT http://myaccount.blob.core.windows.net/$root?restype=container

from azure-sdk-for-java.

actually, if we always specify the root container as $root, the amount code change seems to be minimum.

from azure-sdk-for-java.