swift/api-ref/source/metadata_header_encoding.inc

The metadata value must be UTF-8-encoded and then
URL-encoded before you include it in the header.
This is a direct violation of the HTTP/1.1 `basic rules
<http://www.w3.org/Protocols/rfc2616/rfc2616-sec2.html#sec2.2>`_.
Corrections for the API specifications in api-ref Fixes a number of technical issues with the api-ref section including: - Added missing headers - The header descriptions were made specific to whether they are used in requests or responses and the verb in question (example: Content-Length in object HEAD is the object size, not the response body length). - Added references to API features such as bulk delete. - Many typographical fixes (e.g., spaces in the middle of header names) - Restored xml and json account/container listing examples. The following areas were not updated and it is proposed to defer them to a subsequent update. This is because I don't have time or their merit is debatable: - ACLs (as used in a Keystone context) are not described. - Account create/delete is not described. - I left List Endpoints as-is. Change-Id: I315b4e550b7d10880fbc00fce9311127ba609c2d 2016-08-12 15:52:55 +01:00			`The metadata value must be UTF-8-encoded and then`
			`URL-encoded before you include it in the header.`
			This is a direct violation of the HTTP/1.1 `basic rules
			<http://www.w3.org/Protocols/rfc2616/rfc2616-sec2.html#sec2.2>`_.