@trwnh Yeah, for most people, URIs aren't used outside of HTML, so it's easy to assume that URIs only ever behave like they do in HTML, especially HTML forms. Same about Javascript, it used to be oddly difficult (back around 2005) to find books about Javascript that didn't assume an HTML execution environment (with DOM and all that).

@trwnh
Your Child on the Nice List? Send Them a Letter from Santa! - Shop Now
https://shorturl.at/8Hvy8

Ah wait, I found it -- it seems to have come about because of HTML 2.0 form encoding (application/x-www-form-urlencoded)

Hypertext Markup Language - 2.0 - Table of Contents

(www.w3.org)

and also likely popularized by QUERY_STRING for cgi-bin stuff

RFC 3875: The Common Gateway Interface (CGI) Version 1.1

The Common Gateway Interface (CGI) Version 1.1 (RFC 3875, )

IETF Datatracker (datatracker.ietf.org)

basically you encode all the form data using = and &

then if method=get you pass that along as the query component

or if method=post then you pass it along as the body of the HTTP request

and i guess it stuck that way despite GET for forms being a Bad Idea.

so in short, it looks like query parameters are just an evolution of form data parameters.

@jbqueru the form thing is really getting to me; i only found any of this out because i was looking at the problem of ordering "query parameters" causing two URIs to be semantically equivalent despite being syntactically different.

@trwnh doesn't that kind of depend on the type of form? Classically for a something like a search GET would be a more appropriate method than POST or PUT …

@oblomov maybe? i can see arguments for search being a POST.

@oblomov the semantic argument might be that GET is appropriate for when you want to refer to a query itself, for example using /search?bananas to search for "bananas". but the problems with GET are numerous:

- query components are often logged, while request bodies are not
- query components are limited in how complex they can get -- it's not easy to represent arrays, maps, hierarchical data, and so on
- search may be an expensive request, so better to not allow any old browser to do it

@trwnh
Credit Card Debt over $20k? We Can Help - No Return pay
https://shorturl.at/6s7Ze

@trwnh
#1 Weird Trick To End Tinnitus This Thanksgiving In Just 30 Seconds A Day
https://shorturl.at/E3GNR

@trwnh
“Night Vision” Glasses Help Seniors Drive Safely At Night - Buy Now
https://shorturl.at/w7hNH

@trwnh Unless I'm mistaken it's part of the CGI spec not URI spec.

@dalias yeah i figured this out downthread -- it's HTML 2.0 forms and application/x-www-url-formencoded when the form method=get

CGI also popularized it as well, although CGI takes the opaque QUERY_STRING so the convention mostly arises from html form encoding

@trwnh hm I'm not convinced. The main issue is that neither POST nor PUT are conceptually appropriate. Among the methods defined by HTTP, GET is the one that's conceptually closest. OTOH, those *are* problems with using a query string. Maybe they could be reduced by other means, such as additional headers or body payload (GET *can* have a payload)

@trwnh
ENENCE Instant Translator: Any Language, Any Country
https://shorturl.at/QSb7Z

@oblomov well POST is "do something" not necessarily "create something". https://www.rfc-editor.org/rfc/rfc9110.html#section-9.3.3

> process the representation enclosed in the request according to the resource's own specific semantics

imo "take this request, parse some params out of it, then perform the action" is a valid way of thinking about search.

as for GET,

> requests transfer of a current selected representation for the target resource

is often but not always appropriate. depends on if you see results as a resource.

@oblomov

and that's what it really comes down to imo -- the use of a query component fundamentally alters the identity, you are asking for a different resource when you append the query component. /search and /search?query are different resources.

@trwnh
Greater than $20k in Credit Card Debt -- We Can Help
https://shorturl.at/toZJL

@trwnh oh good point, so if it's done by GET it *must* include the query parameters in the URL. And yeah, now I can see better why POST would be a better choice.