Re: SwiftApi ObjectApi.put behavior on 4xx/5xx responses

2014-12-10 Thread Everett Toews
Enable logging to see the full request/response and the status codes. http://jclouds.apache.org/reference/logging/ Everett On Dec 10, 2014, at 7:58 AM, Daniel Hsueh daniel.hs...@seagate.commailto:daniel.hs...@seagate.com wrote: Hello, Using the new openstack-swift API, I believe the

Re: SwiftApi ObjectApi.put behavior on 4xx/5xx responses

2014-12-10 Thread Everett Toews
I’m not exactly sure what feature you’re requesting at this point. From reading your original question I’d think that the following code would handle it. HttpResponseException.getResponse().getStatusCode() If you’d like to request a feature, you can head over to JIRA [1] and create an issue.

Re: SwiftApi ObjectApi.put behavior on 4xx/5xx responses

2014-12-10 Thread Ignasi Barrera
I see what you say, Daniel. The returned value has changed. Old swift API was using the ParseETagHeader class [1] to parse the response for the putObject request, but the new one is using the ETagHeader class [2] for that purpose. The former threw an exception if the etag wasn't present but the

Re: SwiftApi ObjectApi.put behavior on 4xx/5xx responses

2014-12-10 Thread Daniel Hsueh
I filed feature request https://issues.apache.org/jira/browse/JCLOUDS-793 Yes, the ParseETagHeader class throws an exception, but this doesn't report what went wrong; it could be the blobstore is broken and omitted the etag! (yes, highly unlikely, but a precise response would be much more useful)