4 ms·
Is GET with a request body impractical at this point? It has historically been frowned upon [1] but is it really too late to change that convention? [1]: https
by divbzero 5y ago
Is GET with a request body impractical at this point? It has historically been frowned upon [1] but is it really too late to change that convention?
[1]: https://stackoverflow.com/questions/978061/http-get-with-request-body https://stackoverflow.com/questions/978061/http-get-with-req...
- asplake 5y agohttps://news.ycombinator.com/item?id=30129631 https://news.ycombinator.com/item?id=30129631
- freedomben 5y agoI've seen this done a few times and in most of those cases I agreed it made sense. I've thought about this myself a few times too. But it does lead to unexpected behavior. Users are trained to copy/paste links and send them. If the body only included stuff like auth tokens then it would be ok, but if relevant query stuff was in there (like page size, for example) that would lead to different results that would ultimately be deleterious IMHO.
- divbzero 5y agoThe copy/paste URL use case is a fair consideration. The places where I’ve seen request bodies on GET requests are APIs [2] that are not seen by the end user. [2]: https://www.elastic.co/guide/en/elasticsearch/reference/6.8/search-request-body.html https://www.elastic.co/guide/en/elasticsearch/reference/6.8/...