2 ms·
> Well, it means that I can easily program all my web services to accept both GET and POST (normally without changing any of my server side code, to seamlessly
by crooked-v 8y ago
> Well, it means that I can easily program all my web services to accept both GET and POST (normally without changing any of my server side code, to seamlessly accept either)
...unless you've got more params than can fit into the de facto URL length limits of browsers (~2K characters for Internet Explorer), in which case you're stuck with POST.
- pdonis 8y agoOr if the request has side effects, which GET requests are not supposed to per the HTTP RFCs.
- ArchTypical 8y agoRFCs are often useful guidelines, but don't get too hung up on them. There are always side effects. eg resource usage, interaction effects (cache priming), etc. [Edit:] > The point is that GET is not supposed to change the information stored on the server side. The RFCs for HTTP USAGE are guidelines that are less about utility and more of an interoperability dream that was never realized. There's nothing sancrosanct about them. There have been DECADES of usage contrary (eg medical, gamedev, advertising, ERP, etc). At some point people realize it's bikeshedding issue that's more trouble than it's worth.
- pdonis 8y ago> There are always side effects. eg resource usage, interaction effects (cache priming), etc. "Side effects" probably isn't the best term for what I meant. The point is that GET is not supposed to change the information stored on the server side.