This turned out to be a known issue with swath.
I upgraded to a newer version and the problem was resolved :)
Mvh / Best regards
Morten Møller Riis
Gigahost ApS
m...@gigahost.dk
On Jul 11, 2013, at 10:52 AM, Morten Møller Riis wrote:
> I use swauth, and thus authtoken is not present in my p
I use swauth, and thus authtoken is not present in my pipeline. This might be
why I'm seeing the problem actually.
Mvh / Best regards
Morten Møller Riis
Gigahost ApS
m...@gigahost.dk
On Jul 11, 2013, at 4:04 AM, Shrinand Javadekar wrote:
> I had a similar problem. See [1]. The fix was to ad
I had a similar problem. See [1]. The fix was to add delay_auth_decision =
1 in the proxy-server.conf
[filter:authtoken]
...
delay_auth_decision = 1
-Shri
[1] https://answers.launchpad.net/swift/+question/225614
On Wed, Jul 10, 2013 at 4:43 AM, Morten Møller Riis wrote:
> I've been looking at
I've been looking at tempurl.py and found that the problem occurs here:
def _get_key(self, env, account):
"""
Returns the X-Account-Meta-Temp-URL-Key header value for the
account, or None if none is set.
:param env: The WSGI environment for the request.
I'm having trouble getting tempurl to work.
I set the "X-Account-Meta-Temp-Url-Key" metadata on the account. And a GET
request shows it's set correctly.
I've enabled it on the proxy server in /etc/swift/proxy-server.conf:
[DEFAULT]
bind_port = 8080
workers = 8
user = swift
[pipeline:main]
pipe
thanks for the help.
along with your, and other people's in #openstack-swift on irc, we fixed it.
i had not added tempurl to the pipeline in proxy-server.conf. once that was
fixed, it worked immediately on 1.7, but not on 1.4 which started saying "500
Internal Server Error". after some more tinke
I upgraded our test cluster to 1.7.4, and still have the same issue.
I also bumped the expires to time() + 600 and made sure the clocks on client
and servers are in sync to the second (client was 2 minutes off earlier)
but so that didn't change anything. expires is def. higher than the current
ti
Hi,
using swift 1.4.8 on Centos machines. (latest packages for centos. note that
i'm assuming tempurl works with this version merely because all the code seems
to be there, i couldn't find clear docs on whether it should work or not?)
I want to use the swift tempURL feature as per
http://failver
ault, Jason (Cloud Services)
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] Swift: tempURL
On Tue, May 15, 2012 at 4:46 PM, Rouault, Jason (Cloud Services)
wrote:
> There is a blueprint for this work in Keystone Folsom
Review is up: https://review.openst
On Tue, May 15, 2012 at 4:46 PM, Rouault, Jason (Cloud Services)
wrote:
> There is a blueprint for this work in Keystone Folsom
Review is up: https://review.openstack.org/7446
Chmouel.
___
Mailing list: https://launchpad.net/~openstack
Post to : o
Subject: [Openstack] Swift: tempURL
I am trying to run swift temp url feature. We have keystone as identity
service.
Does this feature works with keystone?
I am always getting "no such file or directory".
I am following all the steps generate the tempURL.
I will appr
tempurl dose not work with keystone. you must follow the instruction of
tempurl to use it. the instruction is locate in the comment of
swift/common/middleware/tempurl.py
在 2012-5-15 上午2:06，"Suchi Sinha (susinha)" 写道：
> I am trying to run swift temp url feature. We have keystone as
> identity s
I am trying to run swift temp url feature. We have keystone as
identity service.
Does this feature works with keystone?
I am always getting "no such file or directory".
I am following all the steps generate the tempURL.
I will appreciate any help.
Thanks.
~Suchi
13 matches
Mail list logo
