> Using POST where GET should have been used hasn't caused horrendous bugs in the same way, but it still introduces annoyances. In my experience, "using POST w

> Using POST where GET should have been used hasn't caused horrendous bugs in the same way, but it still introduces annoyances. In my experience, "using POST where GET should have been used" is normally a consequence of URL length limits and HTTP not supporting request bodies for GET. I've never understood the latter decision.