5 ms·
> This, kids, is why GET requests should be idempotent. I'm not sure I understand. What is this referring to?
by Filligree 3y ago
> This, kids, is why GET requests should be idempotent.
I'm not sure I understand. What is this referring to?
- ApeTheRick 3y agoI think the twitter link is messed up, I have to scroll up to see the whole thread. Edit: Fixed the link now.
- tjoff 3y agoTwitter threads are always messed up if you don't have an account. You can't follow the thread at all.
- bombcar 3y agohttps://threadreaderapp.com/thread/990684453734203392.html https://threadreaderapp.com/thread/990684453734203392.html Had a GET request that would open or close the garage door. Safari learned he liked that page, and would hit it every time he opened a new tab on any device.
- Filligree 3y agoAh, I see... POST requests should be idempotent, ideally. PUT requests certainly must be; it's their defining characteristic. GET requests, though, just shouldn't have side-effects at all. (A /toggle URL isn't idempotent. If it were /open and /close it would be, but still shouldn't be GET.)
- bombcar 3y agoYeah I think people are saying "GET shouldn't change state" and using idempotent incorrectly (which is more "hitting this multiple times shouldn't change things more than once").