[ https://tools.oasis-open.org/issues/browse/ODATA-586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37594#comment-37594 ]
Michael Pizzo commented on ODATA-586:
-------------------------------------
Error messages, especially 400 bad request, were not intended to be prescriptive. We should just fix the wording to allow 405 for this case.
> Allow 405 Method Not Allowed when attempting to delete a non-nullable value
> ---------------------------------------------------------------------------
>
> Key: ODATA-586
> URL: https://tools.oasis-open.org/issues/browse/ODATA-586
> Project: OASIS Open Data Protocol (OData) TC
> Issue Type: Improvement
> Components: OData Protocol
> Affects Versions: V4.0_CS02
> Environment: [Proposed]
> Reporter: Michael Pizzo
> Priority: Minor
> Fix For: V4.0_ERRATA01
>
>
> According to 11.4.9.2 in [Core], A DELETE request to a non-nullable value MUST fail and the service respond with 400 Bad Request.
> An equally good response code would be 405 Method Not Allowed.
--
This message was sent by Atlassian JIRA
(v6.2.2#6258)