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
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.
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
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)
Forwarding to user@Š
Hi Alka!
It could be one of the following scenarios you are running in to:
- the extension is not available in your OpenStack installation
- the user does not have an Admin role to access this specific API
Does the extension show up when executing this code?
Just to complete Jeremy's checklist, also make sure you're connecting to
the admin endpoint; double check the port. IIRC that extension is not
exposed in the default endpoint.
El 10/12/2014 18:35, Jeremy Daggett jeremy.dagg...@rackspace.com
escribió:
Forwarding to user@Š
Hi Alka!
It could be
Hi Alka,
Yes, definitely access the Admin endpoint for this functionality! There is
an example [1] of using the Keystone Admin APIs that you can use as an
additional reference.
Thanks for pointing that out Ignasi!
/jd
[1]
