Oh cool.. Didn't know about this. Will try this out.
On Tue, Apr 30, 2013 at 1:37 PM, Samuel Merritt wrote:
> The tempurl key is just a metadata attribute on the account with a
> particular name. swiftclient already supports setting metadata on accounts
> (and containers and objects); no change
The tempurl key is just a metadata attribute on the account with a
particular name. swiftclient already supports setting metadata on
accounts (and containers and objects); no changes are needed.
$ swift post -m temp-url-key:correcthorsebatterystaple
On 4/30/13 10:43 AM, Shrinand Javadekar wrot
Thanks for the reply John.
We have seen a few customers struggle when setting up tempurl. Its easy to
make them edit the proxy-server.conf file. But explaining the second step
is a bit tedious and error-prone. I've been thinking of having a python
script that does this. But something official woul
There are no plans to change the current implementation of tempurl.
In order to generate a tempurl that can be validated without relying on a
network call to a centralized authority service, the owner and the service must
have a shared secret. In the tempurl feature, this shared secret is set as
Hi,
Configuring tempurl in openstack Swift requires two steps:
1) Adding tempurl to the pipeline in proxy-server.conf
2) Setting the tempurl key on the account.
Step #1 above is fairly straight forward. However, step #2 is slightly
complicated; at least as per [1]. It requires first authenticati
5 matches
Mail list logo
