Product Documentation articleHTTP request headers: lq851
Added by IBM contributorTao YT Yan | Edited by IBM contributorXiang Yu Hao on April 28, 2011 | Version 3
Rate this article 1 starsRate this article 2 starsRate this article 3 starsRate this article 4 starsRate this article 5 stars

No abstract provided.


The following table shows the headers that are recognized, wherever applicable on each operation.

SlugContains path and title of the resource. Non-ASCII characters can appear in this header. But they must be properly encoded according to the RFC 2047.
Content-TypeUsed to specify the Mime type for the content being sent to the server. POST and PUT operations will return HTTP response code 400 (Bad request) when this header is not present in the incoming request. If the collection does not support the specified content type, the server will return HTTP response code 415 (Unsupported media type).
Content-LanguageUsed to specify the language for the content being sent to the server. All content is handled via UTF-8 encoding on the server.
Content-LengthUsed to specify the content length when sending media content. This is required when sending media; otherwise HTTP response code 411 (Length required) will be returned.
X-Method-OverrideUsed when tunneling PUT and DELETE requests over POST