-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major
-
None
-
Affects Version/s: None
-
Component/s: REST/AtomPub Binding
-
None
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.