> and user-controlled
replyI've found some sites that tack on a session ID and if you try to tamper with the URL in any way, it sends you back to "Page 1" really annoys me lol at that point let me skip to any page with your web UI.
Well, because it is more code. Current caching software caches by headers + query string. It now needs to be expaned to cache by body too.
replyIt feels very pointless and there is no drawback of just using POST
There is: your browser or other type of client does not know it can repeat a POST request if it fails, whereas a QUERY request can be freely repeated in case of errors.
replyIs caching not the primary reason to use this over POST? You should never want to cache POST requests.
reply