3 ms·
> but a web service creator can decide otherwise This is like "undefined behavior" in C. Sure, you can make a GET have side effects in your application, but ev
by cesarb 7y ago
> but a web service creator can decide otherwise
This is like "undefined behavior" in C. Sure, you can make a GET have side effects in your application, but everything else will still assume that HEAD and GET is free of side effects, and might repeat requests, omit requests (using cached data), or even do requests speculatively in advance.
- csunbird 7y agoThis reminds me of the story of an internet connected garage door opener that uses GET for opening and closing > https://twitter.com/rombulow/status/990684453734203392?lang=en https://twitter.com/rombulow/status/990684453734203392?lang=... TL;DR: Safari figures out the user is visiting this page very frequently so whenever Safari opens, it tries to send a request to fetch the garage door "page" link before he visits anywhere to cache the response. Which immediately opens the garage door.