[OASIS Issue Tracker] Created: (CMIS-29) Location header inexamples

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

Location header in examples
---------------------------

                 Key: CMIS-29
                 URL: http://tools.oasis-open.org/issues/browse/CMIS-29
             Project: OASIS Content Management Interoperability Services TC
          Issue Type: Bug
          Components: REST/AtomPub Binding
            Reporter: Julian Reschke
            Assignee: Al Brown


It appears that the Location response headers in most examples are incorrect (copy & paste issue?).

For instance, setContentStream has:

PUT /edit-media/atom03 HTTP/1.1
Host: example.org
User-Agent: Thingio/1.0
Authorization: Basic ZGFmZnk6c2VjZXJldA==
Content-Type: xxxx/yyyy
Content-Length: nnn 

Response:

HTTP/1.1 200 OK
Date: Fri, 12 July 2007 17:17:17 GMT
Content-Type: application/atom+xml;type=entry
Content-Length: nnn
ETag: "abcdefghijkl1"
Location: http://example.org/edit/atom03

In general, for PUT->2xx, the only legal Location header value would be one that is identical to the RequestURI.



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira