[
https://issues.apache.org/jira/browse/JCLOUDS-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Gaul updated JCLOUDS-255:
--------------------------------
Description:
Some blob store providers allow using signed requests in two forms: either with
an Authorization header or with query parameters. Using the query parameter
form of the signed request is necessary for clients that don't support adding a
header or for returning a redirect where the Authorization header would be
removed.
The jclouds atmos, aws-s3, and azure implementations generate signed requests
only with the Authorization header, while cloudfiles-us, hpcloud-objectstorage
use query parameters. Ideally the BlobRequestSigner interface would allow the
user to decide which form of signed request to create.
was:
Some blob store providers allow using signed requests in two forms: either with
an Authorization header or with query parameters. Using the query parameter
form of the signed request is necessary for clients that don't support adding a
header or for returning a redirect where the Authorization header would be
removed.
The jcouds atmos, aws-s3, and azure implementations generate signed requests
only with the Authorization header, while cloudfiles-us, hpcloud-objectstorage
use query parameters. Ideally the BlobRequestSigner interface would allow the
user to decide which form of signed request to create.
> atmos, aws-s3, azure blob signers doesn't support query parameter
> authentication
> --------------------------------------------------------------------------------
>
> Key: JCLOUDS-255
> URL: https://issues.apache.org/jira/browse/JCLOUDS-255
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-blobstore
> Affects Versions: 1.6.2
> Reporter: Kevin Krouse
> Priority: Minor
>
> Some blob store providers allow using signed requests in two forms: either
> with an Authorization header or with query parameters. Using the query
> parameter form of the signed request is necessary for clients that don't
> support adding a header or for returning a redirect where the Authorization
> header would be removed.
> The jclouds atmos, aws-s3, and azure implementations generate signed requests
> only with the Authorization header, while cloudfiles-us,
> hpcloud-objectstorage use query parameters. Ideally the BlobRequestSigner
> interface would allow the user to decide which form of signed request to
> create.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
