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.
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.