3 ms·

I've heard this. I am clear why it is true. I would appreciate it if you could explain. :-) I'm not clear why using parameters in the GET request body would

I've heard this. I am clear why it is true. I would appreciate it if you could explain. :-) I'm not clear why using parameters in the GET request body would do weird things with the cache but using parameters in the POST request body will not hit these issues.

sethammons 7y ago
In general: GET can have caching, POST should not. However, if you are dealing with internal only systems, it doesn't really matter. Browsers and some tools have optimizations and expectations around what can be done with different HTTP verbs. Maybe your load balancer could see the same GET request and serve a cached value (as long as it counts the body in its caching logic). If you are not hoping to take advantage of GET caching, just stick with a POST.