openstack team mailing list archive

[Jeff Kramer <jeffkramer@xxxxxxxxx>]

Michael,

You want something like this:

swift -A https://swift.auth.url/auth/v1.0 -U <account:user> -K <key>
post -r .r:* <container>

Then you can access the files using your AUTH id, for example:

https://swift.auth.url/v1/AUTH_511636fe-30f6-411c-974d-caf3760b4bc4/<container>/<object>

On Tue, Jul 12, 2011 at 5:14 PM, Michael Szilagyi <mszilagyi@xxxxxxxxx> wrote:
>
> Does anyone know how one would go about setting a Swift container as public (as in no auth required to snag objects stored within it).  Based on some of the documentation I've read it seems like maybe one would have to set the X-Container-Read ACLs to some sort of wildcard and then use a custom authorization handler in order to bypass the normal auth scheme.  I'm not really sure if that's the desired way to go about it or if there's an easier way that doesn't involve writing custom authorization handlers.
> Any insight would be appreciated!
> -Mike.
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>



--
Jeff Kramer
jeffkramer@xxxxxxxxx
http://www.jeffkramer.org/