jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-1271) Remove signRemoveBlob
Date Thu, 20 Apr 2017 01:11:04 GMT

    [ https://issues.apache.org/jira/browse/JCLOUDS-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15975867#comment-15975867

ASF subversion and git services commented on JCLOUDS-1271:

Commit 2e7de9f850bfc699ccd4df313c3dfe42be87f501 in jclouds's branch refs/heads/master from
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=2e7de9f ]

JCLOUDS-1271: Deprecate signRemoveBlob

URL signing should always use authentication parameters instead of
headers yet no provider supports DELETEs with the former.

> Remove signRemoveBlob
> ---------------------
>                 Key: JCLOUDS-1271
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1271
>             Project: jclouds
>          Issue Type: Improvement
>          Components: jclouds-blobstore
>    Affects Versions: 2.0.1
>            Reporter: Andrew Gaul
>            Assignee: Andrew Gaul
>            Priority: Minor
> URL signing is intended to vend URLs that external clients can use to interact with object
stores without routing through jclouds.  This makes sense for {{signGetBlob}} and {{signPutBlob}}
but jclouds also offers {{signRemoveBlob}}.  The latter is a misfeature since signed URL should
use only URL parameters yet no provider supports this for DELETEs.  Deprecate in 2.1.0 and
remove in 2.2.0.

This message was sent by Atlassian JIRA

View raw message