@@ -367,7 +369,7 @@ limit The amount of results requested (default is 10000)
marker Return containers with name lexicographically after marker
format Optional extended reply type (can be ``json`` or ``xml``)
shared Show only shared containers (no value parameter)
public Show only public containers (no value parameter)
public Show only public containers (no value parameter / avalaible only for owner requests)
until Optional timestamp
====================== =========================
...
...
@@ -542,8 +544,8 @@ delimiter Return objects up to the delimiter (discussion follows)
path Assume ``prefix=path`` and ``delimiter=/``
format Optional extended reply type (can be ``json`` or ``xml``)
meta Return objects that satisfy the key queries in the specified comma separated list (use ``<key>``, ``!<key>`` for existence queries, ``<key><op><value>`` for value queries, where ``<op>`` can be one of ``=``, ``!=``, ``<=``, ``>=``, ``<``, ``>``)
shared Show only shared objects (no value parameter)
public Show only public containers (no value parameter)
shared Show only objects (no value parameter)
public Show only public objects (no value parameter / avalaible only for owner reqeusts)
@@ -1136,6 +1138,8 @@ Read and write control in Pithos is managed by setting appropriate permissions w
A user may ``GET`` another account or container. The result will include a limited reply, containing only the allowed containers or objects respectively. A top-level request with an authentication token, will return a list of allowed accounts, so the user can easily find out which other users share objects. The ``X-Object-Allowed-To`` header lists the actions allowed on an object, if it does not belong to the requesting user.
Shared objects that are also public do not expose the ``X-Object-Public`` meta information.
Objects that are marked as public, via the ``X-Object-Public`` meta, are also available at the corresponding URI returned for ``HEAD`` or ``GET``. Requests for public objects do not need to include an ``X-Auth-Token``. Pithos will ignore request parameters and only include the following headers in the reply (all ``X-Object-*`` meta is hidden):