News for hackers. Stuff that matters.

A comment on I've been abusing HTTP Status Codes in my APIs for years. Parent comment

Re:I've been abusing HTTP Status Codes in my APIs for years by guhcampos on Wednesday July 13, 2022 @11:42AM (#32084247)
I'd say this makes the author's point entirely valid, it only shifts the argument in a broader direction: it's not the application abusing HTTP status codes: it's the REST standard itself.

Why, in all fairness, we always knew. It's an overloading of an existing technology, a bit hacky as it is, and stuff like GRPC are the answer to this, but still the simplicity of HTTP and REST are the demise of standardization.

[ Parent | on HN ]
Re:I've been abusing HTTP Status Codes in my APIs for years by dragonwriter on Wednesday July 13, 2022 @12:27PM (#32084915)
> it's the REST standard itself.

REST is an architectural style, not a standard.

> It's an overloading of an existing technology, a bit hacky as it is

REST is not tied to a particular technology or protocol, and is not “overloading” whatever protocol(s) it is used with; the architectural style specifies using the subset of the available features of the underlying protocols that corresponds to REST semantics consistent with the specifications of those protocols.

[ Parent | on HN ]