[
https://issues.apache.org/jira/browse/JCLOUDS-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13707109#comment-13707109
]
Andrew Gaul commented on JCLOUDS-187:
-------------------------------------
Jeremy would you like to take a crack at this?
> ParseSwiftErrorFromHttpResponse.handleError should throw
> ContainerNotFoundException instead of KeyNotFoundException in all situations
> where container does not exist
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JCLOUDS-187
> URL: https://issues.apache.org/jira/browse/JCLOUDS-187
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-blobstore
> Affects Versions: 1.6.1
> Reporter: Andrew Gaul
> Priority: Minor
>
> ParseSwiftErrorFromHttpResponse.handleError always throws
> KeyNotFoundException for blob operations reporting 404. Could it parse the
> response from Swift and throw ContainerNotFoundException instead?
> $ bin/jclouds-cli-1.6.1-incubating/bin/jclouds blobstore container-exists
> gaul-fakecontainer
> Container not found: gaul-fakecontainer not found: while checking existence
> $ bin/jclouds-cli-1.6.1-incubating/bin/jclouds blobstore write
> gaul-fakecontainer blob input
> Blob not found: blob not found in container gaul-fakecontainer: <html><h1>Not
> Found</h1><p>The resource could not be found.</p></html>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
