| ▲ | PunchyHamster 6 hours ago | |
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. It feels very pointless and there is no drawback of just using POST | ||
| ▲ | OvervCW 6 hours ago | parent | next [-] | |
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. | ||
| ▲ | afavour 6 hours ago | parent | prev [-] | |
Is caching not the primary reason to use this over POST? You should never want to cache POST requests. | ||