| 2013-01-31 00:41:51 |
Byron McCollum |
description |
When uploading an object, swift client will attempt to first ensure the container exists before uploading the object. This is great, and a wonderful convenience, unless you happen to be a lowly non-admin user. In that case, you get an ugly error saying you are not authorized to create the container*, but your object is successfully uploaded. This of course assumes you have been granted write access to the container.
* Which causes all kinds of confusion, because the error doesn't reflect the action the user was taking. The user was uploading an object, then all of a sudden they get an error about not being about to create container, overlooking the fact the object had indeed been uploaded. |
When uploading an object, swift client will attempt to first ensure the container exists before uploading the object. This is great, and a wonderful convenience, unless you happen to be a lowly non-admin user. In that case, you get an ugly error saying you are not authorized to create the container*, but your object is successfully uploaded. This of course assumes you have been granted write access to the container.
* Which causes all kinds of confusion, because the error doesn't reflect the action the user was taking. The user was uploading an object, then all of a sudden they get an error about not being able to create a container, one that happens to already exist, and overlooking the fact the object had indeed been uploaded. |
|
