Revision af7bb62f docs/source/devguide.rst

b/docs/source/devguide.rst
36 36 
\                          Always reply with the MD5 in the ETag.
37 37 
\                          Note that ``/login`` will only work if an external authentication system is defined.
38 38 
\                          Include option to ignore Content-Type on ``COPY``/``MOVE``.
39 
\                          Use format parameter for conflict (409) replies.
39 
\                          Use format parameter for conflict (409) and uploaded hash list (container level) replies.
40 40 
0.7 (Nov 21, 2011)         Suggest upload/download methods using hashmaps.
41 41 
\                          Propose syncing algorithm.
42 42 
\                          Support cross-account object copy and move.
......
602 602 
======================  ============================================
603 603 
Request Parameter Name  Value
604 604 
======================  ============================================
605 
format                  Optional hash list reply type (can be ``json`` or ``xml``)
605 606 
update                  Do not replace metadata/policy (no value parameter)
606 607 
======================  ============================================
607 608 

  		





  608
  
  
    
No reply content/headers, except when uploading data, where the reply consists of a list of hashes for the blocks received (in a simple text format, with one hash per line).


  		





  
  609
  
    
No reply content/headers, except when uploading data, where the reply consists of a list of hashes for the blocks received (in the format specified).


  		





  609
  610
  
    

  		





  610
  611
  
    
The operation will overwrite all user defined metadata, except if ``update`` is defined.


  		





  611
  612
  
    
To change policy, include an ``X-Container-Policy-*`` header with the name in the key. If no ``X-Container-Policy-*`` header is present, no changes will be applied to policy. The ``update`` parameter also applies to policy - deleted values will revert to defaults. To delete/revert a specific policy directive, use ``update`` and an empty header value. See container ``PUT`` for a reference of policy directives.


  		












Also available in:
  Unified diff