[OASIS Issue Tracker] Updated: (ODATA-420) Response codes 404 and 405: MUST instead of SHOULD

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

     [ http://tools.oasis-open.org/issues/browse/ODATA-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Drees updated ODATA-420:
-------------------------------

    Resolution: 
https://www.oasis-open.org/committees/download.php/49405/odata-v4.0-wd02-part1-protocol-2013-06-04.docx

Accepted: https://www.oasis-open.org/committees/download.php/49557/odata-meeting-41_on-20130613_14-F2F-minutes.html#odata-420


  was:https://www.oasis-open.org/committees/download.php/49405/odata-v4.0-wd02-part1-protocol-2013-06-04.docx


> Response codes 404 and 405: MUST instead of SHOULD
> --------------------------------------------------
>
>                 Key: ODATA-420
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-420
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData Protocol 
>    Affects Versions: V4.0_CSD01
>         Environment: [Applied]
>            Reporter: Ralf Handl
>            Assignee: Ralf Handl
>             Fix For: V4.0_CSD02
>
>
> It is unclear what the service might do if it doesn't want to respond with 404 Not Found to a non-existing resource or 405 Method Not Allowed for an existing resource.

-- 
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