HTTP request headers
The following table shows the headers that are recognized, wherever applicable
on each operation.
||Contains 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.
||Used 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).
||Used to specify the language for to the
content being sent to the server. All contents are handled via UTF-8 encoding
on the server.
||Used 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.
||Used to validate local cache of feed &
entry documents retrieved before. If the feed / entry is not modified since
the specified date, HTTP response code 304 (Not Modified) is returned.
||Contains ETag response header sent by the
server in a previous request to the same url. If the ETag is still valid
for the specified resource, HTTP response code 304 (Not Modified) is returned.
||Used when tunneling PUT and DELETE requests
over POST |