Thanks Niraj, this fixed my problem! I had looked in the org.jclouds.Constants interface for this exact property, but it makes sense that it would be in the S3Constants interface instead, since virtual host buckets are an S3-specific thing.
Just out of curiosity, is this property documented anywhere online, that I should have found in my search? (Even the interface doesn't have javadoc comments on this property, explaining its purpose.) *Steve Kingsland* Senior Software Engineer *Opower * <http://www.opower.com/> *We’re hiring! See jobs here <http://www.opower.com/careers> * On Mon, Aug 11, 2014 at 8:21 PM, Niraj Tolia <[email protected]> wrote: > The virtual hosts property is your friend here. Just use > -Djclouds.s3.virtual-host-buckets=false on the command line or the > equivalent in your code. > > Cheers, > Niraj > > On Mon, Aug 11, 2014 at 5:19 PM, Steve Kingsland > <[email protected]> wrote: > > I'm trying to use jclouds' S3 API to connect to an internally-hosted Ceph > > server, which exposes an S3-compliant API. Use other (ruby and perl) > > clients, I've noticed that my requests work fine when I put the > > container/bucket name after the hostname, like this: > > > > https://opower.internal/mybucket/?acl > > > > However, jclouds is putting the container name in the hostname (S3 calls > > this a "virtual bucket"), like so: > > > > https://mybucket.opower.internal/?acl > > > > And that's failing with an "AccessDenied" error that I haven't figured > out > > yet, but am still working on. In the mean time, is there a way to > configure > > jclouds to put the container name *after* the host name, in the request? > > > > > > Steve Kingsland > > > > > > Senior Software Engineer > > > > Opower > > > > > > We’re hiring! See jobs here >
