3 ms·

Yes, people who use put and delete (and any other verb other than post and get) come off as insufferable bores to me. Heck, you just use GET and it will work fi

Yes, people who use put and delete (and any other verb other than post and get) come off as insufferable bores to me. Heck, you just use GET and it will work fine 99% of the time.

andybak 4y ago
And that 1% is a killer. Ask the people who had content deleted because of a GET API and bad interactions with pre-fetching and caching.
robertlagrant 4y ago
Having GET commonly understood as idempotent is ergonomic.
- jcelerier 4y ago
  everything that relies on a "common understanding" from humans or ridiculous things like non-compiler-enforced idioms, programming styles, etc. is bound to fail at some point. the only thing that matters is what the PL / system accepts.
  - robertlagrant 4y ago
    Do you think that browsers pre-emptively executing GET requests, or proxies caching GET responses, is a common understanding from humans?
    - jcelerier 4y ago
      Those are just bugs from engineers who assumed that such a common understanding existed. Bug reports should be filled, that's all.
Sohcahtoa82 4y ago
"GET" should not be used for anything that changes state (beyond simple logging of requests). I'm an AppSec engineer and if I were doing a penetration test and found that an endpoint was using GET requests for state changes, I'd consider it a serious enough bug to put it on the report, even if it wasn't a security issue.