A
at1st@mstdn.ca
@at1st@mstdn.ca
Posts
-
#TIL the query component of a URI is actually completely opaque. -
#TIL the query component of a URI is actually completely opaque.@Charrondev @trwnh @oblomov As I understand it, part of the problem is that the order of query parameters means that "search?query=foo&option=bar" caches differently than "search?option=bar&query=foo" - because if you don't do query normalization before caching, they "look" different to the cache.
-
#TIL the query component of a URI is actually completely opaque.@trwnh @oblomov I'd add one additional benefit: they're infinitely easier to debug and test.
At least it's pretty common practice as I recall in Java EE to make an HttpServlet, generate doGet/doPost, and have doPost just call doGet, or vice versa.
Then GET URL calls let you diagnose what's being passed to which query parameter.