Ask Your Question

Revision history [back]

I have exactly same problem. I used How do I figure out which version I am using? Is it 1.3 or 1.4.3?

1) Initially I used tempauth - pipeline = healthcheck cache tempauth proxy-server With that swift-proxy-server /etc/swift/proxy-server.conf would not start at all.

root@proxyServer:~# swift-proxy-server /etc/swift/proxy-server.conf /usr/lib/pymodules/python2.6/paste/deploy/ UserWarning: Module netifaces was already imported from /usr/lib/pymodules/python2.6/, but /usr/lib/pymodules/python2.6 is being added to sys.path import pkg_resources root@proxyServer:~# ps aux|grep swift root 2863 0.0 0.1 7624 900 pts/0 S+ 16:00 0:00 grep --color=auto swift ... and no one uses port 8080 ...

2) I changed tempauth to auth [DEFAULT] cert_file = /etc/swift/cert.crt key_file = /etc/swift/cert.key bind_port = 8080 workers = 8 user = swift

[pipeline:main] pipeline = healthcheck cache auth proxy-server

[app:proxy-server] use = egg:swift#proxy allow_account_management = true

[filter:auth] use = egg:swift#auth user_system_root = testpass .admin

[filter:healthcheck] use = egg:swift#healthcheck

[filter:cache] use = egg:swift#memcache memcache_servers =

Now I get < HTTP/1.1 401 Unauthorized < Content-Length: 358 < Content-Type: text/html; charset=UTF-8 < Date: Thu, 11 Aug 2011 23:15:26 GMT < <html> <head> <title>401 Unauthorized</title> </head> <body>

401 Unauthorized

This server could not verify that you are authorized to access the document you requested. Either you supplied the wrong credentials (e.g., bad password), or your browser does not understand how to supply the credentials required.