ISSUE-39: HTTP status codes used for creation
201/202
HTTP status codes used for creation
- State:
- CLOSED
- Product:
- Linked Data Platform Spec
- Raised by:
- Roger Menday
- Opened on:
- 2012-11-19
- Description:
- In section 5.4.1:
"servers MUST respond with status code 201"
can be changed to cover with returning 202 (before 201 later on) ?
does this use of 202/201 make sense ?
see http://lists.w3.org/Archives/Public/public-ldp-wg/2012Nov/0070.html - Related Actions Items:
ACTION-44 on Steve Speicher to [EDITOR] delete 1st sentence of section 5.4.5, and reword the second one as informative - due 2013-04-12, closed- Related emails:
- LDP Rec (from eric@w3.org on 2015-02-20)
- Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (from ashok.malhotra@oracle.com on 2013-04-05)
- ldp-ISSUE-39 (201/202): HTTP status codes used for creation [Linked Data Platform core] (from sysbot+tracker@w3.org on 2012-11-19)
Related notes:
Resolution:
- Delete 1st sentence of section 5.4.5, and reword the second one as informative.
- If the resource was created successfully, the server MUST respond with 201.
See http://www.w3.org/2012/ldp/meeting/2013-03-13#resolution_4
http://www.w3.org/2012/ldp/meeting/2013-03-13#resolution_5
and http://www.w3.org/2012/ldp/meeting/2013-03-13#resolution_6
Display change log
