Revision 5df6c6d1 docs/source/devguide.rst
| b/docs/source/devguide.rst | ||
|---|---|---|
| 25 | 25 |
========================= ================================ |
| 26 | 26 |
Revision Description |
| 27 | 27 |
========================= ================================ |
| 28 |
0.7 (Oct 13, 2011) Suggest upload/download methods using hashmaps.
|
|
| 28 |
0.7 (Oct 17, 2011) Suggest upload/download methods using hashmaps.
|
|
| 29 | 29 |
\ Propose syncing algorithm. |
| 30 | 30 |
\ Support cross-account object copy and move. |
| 31 | 31 |
\ Pass token as a request parameter when using ``POST`` via an HTML form. |
| 32 | 32 |
\ Optionally use source account to update object from another object. |
| 33 | 33 |
\ Use container ``POST`` to upload missing blocks of data. |
| 34 | 34 |
\ Report policy in account headers. |
| 35 |
\ Add insufficient quota reply. |
|
| 35 | 36 |
0.6 (Sept 13, 2011) Reply with Merkle hash as the ETag when updating objects. |
| 36 | 37 |
\ Include version id in object replace/change replies. |
| 37 | 38 |
\ Change conflict (409) replies format to text. |
| ... | ... | |
| 763 | 764 |
|
| 764 | 765 |
The ``X-Object-Sharing`` header may include either a ``read=...`` comma-separated user/group list, or a ``write=...`` comma-separated user/group list, or both separated by a semicolon (``;``). Groups are specified as ``<account>:<group>``. To publish the object, set ``X-Object-Public`` to ``true``. To unpublish, set to ``false``, or use an empty header value. |
| 765 | 766 |
|
| 766 |
=========================== ============================== |
|
| 767 |
Return Code Description |
|
| 768 |
=========================== ============================== |
|
| 769 |
201 (Created) The object has been created |
|
| 770 |
409 (Conflict) The object can not be created from the provided hashmap, or there are conflicting permissions (a list of missing hashes, or a list of conflicting sharing paths will be included in the reply - in simple text format) |
|
| 771 |
411 (Length Required) Missing ``Content-Length`` or ``Content-Type`` in the request |
|
| 772 |
422 (Unprocessable Entity) The MD5 checksum of the data written to the storage system does not match the (optionally) supplied ETag value |
|
| 773 |
=========================== ============================== |
|
| 767 |
============================== ============================== |
|
| 768 |
Return Code Description |
|
| 769 |
============================== ============================== |
|
| 770 |
201 (Created) The object has been created |
|
| 771 |
409 (Conflict) The object can not be created from the provided hashmap, or there are conflicting permissions (a list of missing hashes, or a list of conflicting sharing paths will be included in the reply - in simple text format) |
|
| 772 |
411 (Length Required) Missing ``Content-Length`` or ``Content-Type`` in the request |
|
| 773 |
413 (Request Entity Too Large) Insufficient quota to complete the request |
|
| 774 |
422 (Unprocessable Entity) The MD5 checksum of the data written to the storage system does not match the (optionally) supplied ETag value |
|
| 775 |
============================== ============================== |
|
| 774 | 776 |
|
| 775 | 777 |
|
| 776 | 778 |
COPY |
| ... | ... | |
| 803 | 805 |
|
| 804 | 806 |
| |
| 805 | 807 |
|
| 806 |
=========================== ============================== |
|
| 807 |
Return Code Description |
|
| 808 |
=========================== ============================== |
|
| 809 |
201 (Created) The object has been created |
|
| 810 |
409 (Conflict) There are conflicting permissions (a list of conflicting sharing paths will be included in the reply - in simple text format) |
|
| 811 |
=========================== ============================== |
|
| 808 |
============================== ============================== |
|
| 809 |
Return Code Description |
|
| 810 |
============================== ============================== |
|
| 811 |
201 (Created) The object has been created |
|
| 812 |
409 (Conflict) There are conflicting permissions (a list of conflicting sharing paths will be included in the reply - in simple text format) |
|
| 813 |
413 (Request Entity Too Large) Insufficient quota to complete the request |
|
| 814 |
============================== ============================== |
|
| 812 | 815 |
|
| 813 | 816 |
|
| 814 | 817 |
MOVE |
| ... | ... | |
| 878 | 881 |
|
| 879 | 882 |
| |
| 880 | 883 |
|
| 881 |
=========================== ============================== |
|
| 882 |
Return Code Description |
|
| 883 |
=========================== ============================== |
|
| 884 |
202 (Accepted) The request has been accepted (not a data update) |
|
| 885 |
204 (No Content) The request succeeded (data updated) |
|
| 886 |
409 (Conflict) There are conflicting permissions (a list of conflicting sharing paths will be included in the reply - in simple text format) |
|
| 887 |
411 (Length Required) Missing ``Content-Length`` in the request |
|
| 888 |
416 (Range Not Satisfiable) The supplied range is invalid |
|
| 889 |
=========================== ============================== |
|
| 884 |
============================== ============================== |
|
| 885 |
Return Code Description |
|
| 886 |
============================== ============================== |
|
| 887 |
202 (Accepted) The request has been accepted (not a data update) |
|
| 888 |
204 (No Content) The request succeeded (data updated) |
|
| 889 |
409 (Conflict) There are conflicting permissions (a list of conflicting sharing paths will be included in the reply - in simple text format) |
|
| 890 |
411 (Length Required) Missing ``Content-Length`` in the request |
|
| 891 |
413 (Request Entity Too Large) Insufficient quota to complete the request |
|
| 892 |
416 (Range Not Satisfiable) The supplied range is invalid |
|
| 893 |
============================== ============================== |
|
| 890 | 894 |
|
| 891 | 895 |
The ``POST`` method can also be used for creating an object via a standard HTML form. If the request ``Content-Type`` is ``multipart/form-data``, none of the above headers will be processed. The form should have an ``X-Object-Data`` field, as in the following example. The token is passed as a request parameter. :: |
| 892 | 896 |
|
| ... | ... | |
| 906 | 910 |
|
| 907 | 911 |
| |
| 908 | 912 |
|
| 909 |
=========================== ============================== |
|
| 910 |
Return Code Description |
|
| 911 |
=========================== ============================== |
|
| 912 |
201 (Created) The object has been created |
|
| 913 |
=========================== ============================== |
|
| 913 |
============================== ============================== |
|
| 914 |
Return Code Description |
|
| 915 |
============================== ============================== |
|
| 916 |
201 (Created) The object has been created |
|
| 917 |
413 (Request Entity Too Large) Insufficient quota to complete the request |
|
| 918 |
============================== ============================== |
|
| 914 | 919 |
|
| 915 | 920 |
|
| 916 | 921 |
DELETE |
Also available in: Unified diff