3 ms·
Is caching not the primary reason to use this over POST? You should never want to cache POST requests.
by afavour 4mo ago
Is caching not the primary reason to use this over POST? You should never want to cache POST requests.
- drdexebtjl 4mo agoNo. Being idempotent, it also lets the browser/client/reverse proxy retry it if it fails.
- nfw2 4mo agoTechnically a put or a patch is also idempotent. The benefits are idempotent and safe (and semantically appropriate). Post (generally) communicates something is changing whereas a query doesn't
- gamache 4mo agoPUT is idempotent, PATCH is not always. The semantics of a PATCH payload are up to the server and standards like JSON Patch (RFC 6902, https://datatracker.ietf.org/doc/html/rfc6902 https://datatracker.ietf.org/doc/html/rfc6902) allow non-idempotent operations like adding an item to a list.
- nfw2 4mo agoI stand corrected although using patch this way seems goofy to me.