Reserve the 418 status code

Re:Reserve the 418 status code by snuxoll on Monday August 14, 2017 @10:19AM (#15008713)

And said logic determined your input was invalid, HTTP 400 Bad Request is a perfectly reasonable response.

If you want to use HTTP as nothing more than a transport layer and return 200 OK's all day then fine, but why are you even using HTTP at that point?

[ Parent | on HN ]

Re:Reserve the 418 status code by grandalf on Monday August 14, 2017 @11:13AM (#15009184)

Unless I'm doing some sort of pure REST API I'm simply using HTTP as a transport protocol for my application specific protocol.

If HTTP delivers my application protocol's message successfully, it's an HTTP 2xx, but my application's protocol may have a range of statuses that are not "transport-like" in the way HTTP status codes are, which are the main things that API consumers care about, assuming the basic transport is working.

[ Parent | on HN ]