There are examples in swift.common.middleware of doing this.
If you want to try changing the metadata on the way out you can look at:
https://github.com/openstack/swift/blob/master/swift/common/middleware/staticweb.py#L367-L384
it makes use of the WSGIContext class which allows you to make a
Here's a little script I have to test it out on my SAIO:
#/bin/bash
export PASS='AUTH_tk36accf5200b143dd8883b9841965e6a2'
export URL='http://127.0.0.1:8080/v1/AUTH_dfg'
curl -i -H "X-Auth-Token: $PASS" $URL/hat -XPUT
curl -i -H "X-Auth-Token: $PASS" $URL/hat/one -XPUT -d '1'
curl -i -H "X-A
I'm sorry- I didn't read that part about the proxy restart :) The proxy may
not log if it gets hung up in some middleware. What middleware do you have
running? You can try adding in some log messages into the middleware you have
running to find out where.
On Feb 1, 2013, at 1:37
Sounds like swift isn't listening on that port. What is the bind_port in your
proxy-server.conf?
On Feb 1, 2013, at 12:53 PM, Andrey V. Romanchev wrote:
> Hello!
> I've installed swift + keystone and have incomprehensible problem
>
> First of all I get auth tokens
> curl -d '{"auth": {"tenantN
Just FYI- swift's ratelimiting doesn't limit on bandwidth. Just requests per
second to specific resources.
David
On Mar 30, 2012, at 1:40 PM, Caitlin Bestler wrote:
> Replies inline
>
> -Original Message-
> From: andi abes [mailto:andi.a...@gmail.com]
> Sent: Friday, March 30, 2012
5 matches
Mail list logo
