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 dvlsg on Wednesday July 13, 2022 @11:00AM (#32083659)
Some applications opted for using GET with request bodies as well, for better or worse. Elasticsearch comes to mind.

There have been some attempts to extend the list of http verbs to include something that fits those use cases more naturally - SEARCH and QUERY. QUERY got more traction, if I remember correctly, but I haven't heard much about it in a while.

https://www.w3.org/2012/ldp/wiki/Proposal_for_HTTP_QUERY_Ver...

[ Parent | on HN ]
Re:I've been abusing HTTP Status Codes in my APIs for years by ognarb on Wednesday July 13, 2022 @11:54AM (#32084432)
SEARCH is used by the WebDAV standard, not that I like WebDAV search syntax https://gist.github.com/CarlSchwan/66fde29d52022c0ef76aec362...
[ Parent | on HN ]
Re:I've been abusing HTTP Status Codes in my APIs for years by dragonwriter on Wednesday July 13, 2022 @02:19PM (#32086721)
> SEARCH is used by the WebDAV standard

That’s probably part of the reason the more general one proposed for HTTP is “QUERY” and not “SEARCH”. Also, WebDAV, in following its apparent design philosophy of “more is more”, has multiple different GET-with-(required or optional)-body methods with different purposes: PROPFIND and REPORT as well as SEARCH.

[ Parent | on HN ]
Re:I've been abusing HTTP Status Codes in my APIs for years by yencabulator on Wednesday July 13, 2022 @05:41PM (#32089111)
You might like QUERY: https://www.ietf.org/archive/id/draft-ietf-httpbis-safe-meth...
[ Parent | on HN ]