Timeline for answer to How to pass arguments of a complex search in RESTful API request params by Ewan
Current License: CC BY-SA 4.0
Post Revisions
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 2 at 15:51 | comment | added | JimmyJames | Per the same RFC you link to: "A payload within a GET request message has no defined semantics; sending a payload body on a GET request might cause some existing implementations to reject the request." Passing a body with a GET is a bad idea. It just won't work in a lot of cases and it almost guaranteed to not work with caching infrastucture. | |
| Sep 5, 2025 at 16:13 | comment | added | Ewan | "The best kind of correct" | |
| Sep 5, 2025 at 13:12 | comment | added | Anton Pastukhov | "GET supports a body" - while factually true, the real world support is hit-and-miss. I'd think twice before going this way. POST requests also have a disadvantage of not being copy-pastable and shareable, in contrast with GETs | |
| Sep 3, 2025 at 10:44 | history | answered | Ewan | CC BY-SA 4.0 |