4 ms·
GET requests always change state on the server because we have logs. Furthermore logs are often parsed by XMLparsers which are often error prone.
by neuroelectron 2y ago
GET requests always change state on the server because we have logs. Furthermore logs are often parsed by XMLparsers which are often error prone.
- xg15 2y agoThis is why idempotency is defined through visible state on the server. What happens on the server doesn't matter, but a GET request should not change the results of any subsequent future requests, as visible to the clients. E.g. adding or modifying a post or a blog entry via a GET request would break the rules. (Nothing stops you in practice from ignoring that requirement, but it can lead to ugly surprises, such as a crawler triggering a mass deletion because it crawled the /delete links)