OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

cmis message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] Commented: (CMIS-605) setContentStream (PUT)should return 200 on success, not 201

    [ http://tools.oasis-open.org/issues/browse/CMIS-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763#action_16763 ] 

Al Brown commented on CMIS-605:

Accepted / Clarify - Please see HTTP semantics of PUT (in spec).  E.g., 200 Ok & 204 (Ok no content).  If new resource created, 201.  Others see HTTP spec

> setContentStream (PUT) should return 200 on success, not 201
> ------------------------------------------------------------
>                 Key: CMIS-605
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-605
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Bug
>          Components: REST/AtomPub Binding
>    Affects Versions: Committee Draft 04
>            Reporter: Florent Guillaume
>            Assignee: Al Brown
>            Priority: Minor
> says that a successful PUT of a content stream should return 201 (Created).
> But PUT is for editing known resources, there is no creation involved, and we should be consistent with AtomPub that specifies that 200 (Ok) is returned.

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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]