Re:Some items from my “reliability list”
by msluyter on Thursday July 25, 2019 @11:49AM
(#20526399)
Interesting question. My understanding is that a 400 response indicates that there's something malformed about the request itself such that the server can't/won't process it. Given that in order to decline the card the service has to actually process the request, I'd agree that a 400 is inappropriate.
[ Parent
| on HN ]
The previous definition was 400 means the server can't understand the request. Current one is
>The 400 (Bad Request) status code indicates that the server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).
Of course, a lot of things could be said to be a client error.