Hi Daggett, I think this is similar to the issue I had with google cloud storage resumable uploads where expected response was 308 . these may help you Problem is jclouds consider any response other than 2xx as a problem.
https://github.com/jclouds/jclouds/blob/master/core/src/main/java/org/jclouds/http/internal/BaseHttpCommandExecutorService.java#L104 I had to override redirectRetryHandler with https://github.com/jclouds/jclouds-labs-google/blob/master/google-cloud-storage/src/main/java/org/jclouds/googlecloudstorage/handlers/GoogleCloudStorageRedirectRetryHandler.java Also avoiding setException call https://github.com/jclouds/jclouds-labs-google/blob/master/google-cloud-storage/src/main/java/org/jclouds/googlecloudstorage/handlers/GoogleCloudStorageErrorHandler.java I also had lot of troubles with this untill nacx help me :) On 19 September 2014 00:10, Jeremy Daggett <jeremy.dagg...@rackspace.com> wrote: > Hi devs, > > I have a situation where the OpenStack Heat API [1] returns a 302 redirect > for finding a particular stack: > > /v1/{tenant_id}/stacks/{stack_name} > > This is new territory for the OpenStack APIs and I am not clear on how to > handle it. It looks like the various HTTP annotations [2] are used in > binding the error handlers, so do I just handle it in the switch statement > of the error handler? > > Any help is appreciated! > > /jd > > [1] http://developer.openstack.org/api-ref-orchestration-v1.html#stacks > [2] > https://github.com/jclouds/jclouds/tree/master/core/src/main/java/org/jclouds/http/annotation >
