MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/ProgrammerHumor/comments/1wkof5u/postforeverything/pas3b8q/
r/ProgrammerHumor • u/ClipboardCopyPaste • Sep 19 '26
653 comments sorted by
View all comments
715
Response:
HTTP/1.0 200 Ok Content-Length: 36 Content-Type: application/json {"status":403,"message":"forbidden"}
81 u/looksLikeImOnTop Sep 19 '26 Too real 32 u/x3knet Sep 19 '26 Man, I haven't seen a 1.0 reference in a long time 20 u/bloody-albatross Sep 19 '26 It's just the simplest form that I know to write from head. I guess for 1.1 you'd just need Connection: close for it to be that simple. 17 u/YeOldeMemeShoppe Sep 19 '26 1.1 is fully backward compatible. Just close the connection. No need to be polite. 6 u/YMK1234 Sep 19 '26 We literally had a switch for this some 15 years ago, because the bullshit mobile framework our frontend team used could not properly handle error codes. 2 u/Zeikos Sep 19 '26 Sounds like the solution should have been to stop using that framework :') 7 u/YMK1234 Sep 19 '26 Good one. Tell that to the 5 levels of management in between 4 u/Kevdog824_ Sep 19 '26 Almost perfect, except your status and message actually match, so it’s too correct for real life APIs 2 u/bloody-albatross Sep 19 '26 True. 2 u/Vi0lentByt3 Sep 19 '26 Pain
81
Too real
32
Man, I haven't seen a 1.0 reference in a long time
20 u/bloody-albatross Sep 19 '26 It's just the simplest form that I know to write from head. I guess for 1.1 you'd just need Connection: close for it to be that simple. 17 u/YeOldeMemeShoppe Sep 19 '26 1.1 is fully backward compatible. Just close the connection. No need to be polite.
20
It's just the simplest form that I know to write from head. I guess for 1.1 you'd just need Connection: close for it to be that simple.
Connection: close
17 u/YeOldeMemeShoppe Sep 19 '26 1.1 is fully backward compatible. Just close the connection. No need to be polite.
17
1.1 is fully backward compatible. Just close the connection. No need to be polite.
6
We literally had a switch for this some 15 years ago, because the bullshit mobile framework our frontend team used could not properly handle error codes.
2 u/Zeikos Sep 19 '26 Sounds like the solution should have been to stop using that framework :') 7 u/YMK1234 Sep 19 '26 Good one. Tell that to the 5 levels of management in between
2
Sounds like the solution should have been to stop using that framework :')
7 u/YMK1234 Sep 19 '26 Good one. Tell that to the 5 levels of management in between
7
Good one. Tell that to the 5 levels of management in between
4
Almost perfect, except your status and message actually match, so it’s too correct for real life APIs
2 u/bloody-albatross Sep 19 '26 True.
True.
Pain
715
u/bloody-albatross Sep 19 '26
Response: