I'm aware of using logging to see the full exchange. What I was more interested in was programatically determining what a problem is.
Could we request this as a feature? The HttpResponseException class seems perfect for this kind of reporting. On Wed, Dec 10, 2014 at 9:55 AM, Everett Toews <[email protected]> wrote: > Enable logging to see the full request/response and the status codes. > > http://jclouds.apache.org/reference/logging/ > <https://urldefense.proofpoint.com/v2/url?u=http-3A__jclouds.apache.org_reference_logging_&d=AwMFAg&c=IGDlg0lD0b-nebmJJ0Kp8A&r=LuGmq_BGW1Ye0sNeKcnpg4MzQroKFmLPkrt9SlpYRVk&m=RoxYMb4RWWSV-q5ifKV_4PUly-QOCAVgAZteMC-Puio&s=JNLt4k7RuFqTcf3vh4fJNrMGq5oZLI0zmdvZ7begIU0&e=> > > Everett > > > On Dec 10, 2014, at 7:58 AM, Daniel Hsueh <[email protected]> > wrote: > > Hello, > > Using the new openstack-swift API, I believe the ObjectApi.put() call > always returns an etag, or null, if a response is received. There seems no > way to get an HttpResponseException to see a 4xx/5xx response code, yes? > > -- > Daniel Hsueh -- mailto:[email protected] > <[email protected]> tel:+1-905-287-2167 > > > -- Daniel Hsueh -- mailto:[email protected] <[email protected]> tel:+1-905-287-2167
