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


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

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

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

    [ http://tools.oasis-open.org/issues/browse/ODATA-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=33611#action_33611 ] 

Michael Pizzo commented on ODATA-420:

In general we use "SHOULD" instead of "MUST" for error conditions because there may be multiple error conditions and then the service has no way of complying to multiple mandated errors. I.e., if a request identifies a non-existent resource AND contains an unsupported query option, MUST the service return 404 or 501?

> 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: [Proposed]
>            Reporter: 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


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