News for hackers. Stuff that matters.

A comment on The HTTP QUERY Method specification. Parent comment

Re:The HTTP QUERY Method specification by crooked-v on Saturday May 27, 2023 @04:31PM (#36098010)
With POST, you can't know at a system level if it's safe to cache the response or not.
[ Parent | on HN ]
Re:The HTTP QUERY Method specification by DaiPlusPlus on Saturday May 27, 2023 @04:33PM (#36098026)
Cache-Control response headers?
[ Parent | on HN ]
Re:The HTTP QUERY Method specification by preseinger on Saturday May 27, 2023 @06:20PM (#36098962)
insufficient
[ Parent | on HN ]
Re:The HTTP QUERY Method specification by mnot on Saturday May 27, 2023 @09:55PM (#36100382)
https://httpwg.org/specs/rfc9110.html#POST
[ Parent | on HN ]
Re:The HTTP QUERY Method specification by kortex on Sunday May 28, 2023 @01:06AM (#36101325)
> A cached POST response can be reused to satisfy a later GET or HEAD request. In contrast, a POST request cannot be satisfied by a cached POST response because POST is potentially unsafe; see Section 4 of [CACHING].

So if you are using POST to query, you can't cache the response. You have to resort to POST/GET. With QUERY, you have idempotent requests with cacheable responses you can directly return.

[ Parent | on HN ]
Re:The HTTP QUERY Method specification by mnot on Saturday May 27, 2023 @07:44PM (#36099602)
Cache-Control and Content -Location.
[ Parent | on HN ]