4 ms·

IMO apps that do this have a bug, and possibly a security one. This causes issues with prefetching, bot traffic, caching, CSRF, and just plain violates HTTP sta

IMO apps that do this have a bug, and possibly a security one. This causes issues with prefetching, bot traffic, caching, CSRF, and just plain violates HTTP standards.

pstuart 1y ago
Agreed. Those methods should be treated as idempotent.
- almog 1y ago
  > Those methods should be treated as idempotent Idempotency still implies it can change state on the initial call, which to me feels wrong in the context of GET/HEAD/OPTIONS.
  - Mavvie 1y ago
    Indeed, the correct term here is nullipotent.
pinoy420 1y ago
Not really. If I have a service where I need one click to perform an action and store data. It has to be a GET. You can’t post from a url… purist dogma for the sake of purist dogma
- FireInsight 1y ago
  One click to perform an action and store data? Have you heard of HTML forms with method="post"?
  - whatabtemaillnk 1y ago
    [dead]