I haven't tried other providers yet, but at least for the S3 provider it looks like the URL from .signGetBlob() doesn't include the query parameters specific for that provider and uses the Authorization header instead.
Kevin On Fri, Aug 23, 2013 at 9:01 PM, Andrew Gaul <g...@apache.org> wrote: > Kevin, this is exactly what a signed URL means. I can vouch that > jclouds supports this for Atmos, Azure, S3, and Swift. Note that some > providers give additional features in their signed URL mechanism such as > time-limited and byte-range requests although jclouds does not yet > expose these. > > On Fri, Aug 23, 2013 at 02:16:11PM -0700, Kevin Krouse wrote: >> Is there a helper to get a signed URL that uses query string >> parameters instead of the Authorization header? >> >> Something like this: >> >> http://docs.aws.amazon.com/AmazonS3/latest/dev/RESTAuthentication.html#RESTAuthenticationQueryStringAuth >> http://msdn.microsoft.com/en-us/library/dn140256.aspx >> >> Kevin >> >> >> On Thu, Aug 22, 2013 at 9:11 AM, Andrew Gaul <g...@apache.org> wrote: >> > On Thu, Aug 22, 2013 at 02:50:25PM +0200, Andrew Phillips wrote: >> >> Have a look at the Rackspace examples [1]. Specifically, CloudFilesPublish >> >> and GenerateTempURL could help. One of the cloud-storage-workshop >> >> exercises >> >> [2] also has an example that might be useful. >> > >> > You can also use BlobRequestSigner.signGetBlob which embeds per-blob >> > authentication and allows you to express a time-bound for some >> > providers, including Swift. >> > >> > -- >> > Andrew Gaul >> > http://gaul.org/ > > -- > Andrew Gaul > http://gaul.org/