adding 404 response for deleteing non-existent resource#1029
adding 404 response for deleteing non-existent resource#1029dgeb merged 1 commit intojson-api:gh-pagesfrom lukasoppermann:delete-404-response
Conversation
|
This looks good to me. Any objections @json-api/owners? One question is whether we should say a 404 MAY be returned or SHOULD be returned. I'm tempted to say SHOULD, because HTTP's most recent specification pretty clearly implies that DELETE being idempotent doesn't mean you have to return the same status code each time (which was the argument for MAY in #1023):
But, if there's disagreement on a SHOULD, I don't think that technical debate should hold this up, as we can always strengthen a MAY to a SHOULD later. |
|
Even though I am not part of the owners, I would be in favour of SHOULD. |
|
I am fine strengthening to a SHOULD here as well. I think a MAY is almost meaningless compared with the general catchall response section. |
|
@lukasoppermann please update to SHOULD and then we'll get this merged. |
|
@dgeb updated. |
|
Thanks @lukasoppermann! |
Add missing normative statements from #1029
This PR fixes #1023 which is about a not specified response for a
DELETEto a resource that does not exist.