3 ms·
The name of the request is the only difference from the perspective of HTTP. But it's definitely worth mentioning that POST requests trigger a bunch of browser
by thaumasiotes 5y ago
The name of the request is the only difference from the perspective of HTTP. But it's definitely worth mentioning that POST requests trigger a bunch of browser safety features that aren't triggered by GETs.
- stickfigure 5y agoHTTP doesn't assume the existence of a web browser...
- wanderer_ 5y agoTrue, but your garden-variety command-line utility might not be able to send a POST (like wget, but apparently curl can). Both of these concerns are valid and need to be taken together. GET can be run just like a normal URL and thus is more versatile, but as you probably understand, less secure.
- abhishekjha 5y ago>POST requests trigger a bunch of browser safety features that aren't triggered by GETs. Where do I read about these features getting triggered?
- deleted 5y ago[deleted]