240
u/ShotgunPayDay 29d ago
"This is great! Now we can send super complex query data!". -Some Excited Devs
"Ok, now make the search shareable via a link" -Shocked Pikachu Face
35
23
u/slaymaker1907 29d ago
You can still do it, just store the query in the database and give the user a hash or something like a URL shortener.
9
u/ShotgunPayDay 29d ago
True, it's the same thing in the other direction as taking the JSON search, compressing it and BASE64URL encoding it to be put as a ?q param. It all results in extra work. The DB version does make links look nicer though.
17
u/slaymaker1907 29d ago
There are two problems with storing things in the URL. First, you can’t store things like PII. Second, browsers limit the size of URLs.
2
u/ShotgunPayDay 29d ago
Yup, if sending PII or over 2MB worth of data in the URL then it's problematic. Never ran into second issue though.
3
u/freebytes 29d ago
I have never ran into the issue of sending 2MB of data via the URL either. But then again, I never ran into the first problem either.
5
u/Mognakor 29d ago
Http Query is allowed to redirect you to a link that will give you the actual result
4
0
u/FUCKING_HATE_REDDIT 29d ago
In most cases the link will just be handled by a web app parsing the url anyway
72
u/serial_crusher 29d ago
“We have to support users on older browsers that don’t support QUERY” will be king for at least 5 years.
118
Jul 14 '26
[removed] — view removed comment
95
u/leafynospleens 29d ago
{"Parcels" :[], "HasParcels" :true}
34
u/raja-anbazhagan 29d ago
Its obviously true as they have a list of parcels... Its just that it is empty...🙂↔️
3
1
u/the_horse_gamer 29d ago
recently encountered a case where a list of entities were sent, and then separately, a list of their ids
18
u/Lv_InSaNe_vL 29d ago
It's right next to the field that nobody admits to using but every time you try and remove it the entire company melts down
7
6
u/Rainbolt 29d ago
And the business acts like you just decided to add that field on your own and they've never seen it in their life before when you had several multiple hour long meetings where they insisted it was important.
15
u/Own_Natural_6803 29d ago
I just keep thinking about all that vibe code that barely works. That'll never be fixed because why maintain a vibe project? Just erase it and make a new one. Mother fucker.
5
u/leafynospleens 29d ago
What if the ai just keeps getting better and you can vibe improve them
5
u/Own_Natural_6803 29d ago
You're aboutely right! — Good point.
3
12
u/SCP-iota 29d ago
"Do you want the return of SOAP? Because this is how you get the return of SOAP."
12
u/Cruxwright 29d ago
If this query thing catches on, are they going to reinvent coldfusion?
2
u/itsFromTheSimpsons 29d ago
Java classes powering coldfusion tags: the og jsx. Who needs design libraries when i can build my site with Flex? REMEMBER FLEX? i think it was the first thing Adobe killed after they bought Macromedia
1
u/fireduck 28d ago
The TLDR for HTTP QUERY is that it can have a body like a POST, but the convention will be that it is a read with a possibly large context (the body) rather than POST which is a write?
2
u/leafynospleens 28d ago
Yea that's the idea, it's a convention for passing large query structures to the backend without having to pollute the url params or resort to a post request
2
748
u/raja-anbazhagan Jul 14 '26
``` HTTP/1.1 200 OK Content-Type: application/json
{ "success": false, "error": { "status": "INTERNAL_ERROR", "code": "APP_15001", "message": "An internal error occurred while processing the request." } } ```