AnsweredAssumed Answered

REST-Atom binding

Question asked by sbuckle on Sep 24, 2008
I have been going through the CMIS spec and I have a quick question / observation regarding the REST-Atom binding. In the spec it states that arguments can be supplied in either the URI or as HTTP headers. If HTTP headers are used them they will have a 'CMIS-' prefix in front of the argument name; there is an example in the spec that looks something like this:


GET /cmis/main?types HTTP/1.1
Host: example.org
User-Agent: Thingio/1.0
Authorization: Basic ZGFmZnk6c2VjZXJldA==
CMIS-type: 1234567
CMIS-returnPropertyDefinitions: false
CMIS-maxItems: 100
CMIS-skipCount: 0

I thought the convention for adding custom HTTP headers was to prefix them with 'X-' to avoid confusion with the standard HTTP headers? E.g. the above snippet should look something like this:


GET /cmis/main?types HTTP/1.1
Host: example.org
User-Agent: Thingio/1.0
Authorization: Basic ZGFmZnk6c2VjZXJldA==
X-CMIS-type: 1234567
X-CMIS-returnPropertyDefinitions: false
X-CMIS-maxItems: 100
X-CMIS-skipCount: 0

For example, Amazon prefix all of their custom headers with 'X-" with their REST APIs, e.g. S3.

- Simon

Outcomes