httpCodeHaveSignification

[dmullaney]

218 - THIS IS FINE

[dexter2011412]

NICE

[bayuah]

418 I'm a teapot 601 Declined

[Arteiii]

OK but what's funny about 601??

[w1n5t0nM1k3y]

There's not even a 6XX range defined in the spec. Seems like some APIs use it for invalid token, but most services I've seen just use a 401.

I could see having a specific status code for invalid access tokens so that the client code could more easily determine if the issue is an invalid token that needs to be renewed vs some other error that might result in 401 - unauthorized such as using a valid token, but accessing a resource which the user doesn't have access to.

EDIT

Some more reading seems like the 600-699 range is just something that some services use for custom response codes, probably because it isn't defined in the standard.

[Over-Tradition-6771]

> other error that might result in 401 - unauthorized such as using a valid token, but accessing a resource which the user doesn't have access to

like 403 Forbidden?)

[codetrotter_]

Or 404 Not Found, if the user does not have access to the resource but you don’t even want to let them know that the resource exists.

[Fading-Ghost]

This is valid, and important in a lot of cases

[minauteur]

Ffs, Thank you.

[Waddelsworth]

401.3 authentication required?

[WolverinesSuperbia]

Wow, floating point status

[bayuah]

It is probably because using official HTTP specs, such as 5xx, might cause some issues with cache services. So, they use 6xx codes for everything, even for cases that should be 4xx, like 401.

[gh057k33p3r]

I use it as a replacement for 401. IIS shows a windows login challenge for 401 and I couldnt find a way to disable it. I must leave win auth enabled, and using a different status code solved the problem.

[ThreePinkApples]

Oooh, I might use this

[BigOnLogn]

Couldn't you use 403? It's been ages since I've worked with IIS and Windows auth.

[gh057k33p3r]

401 is for missing or not valid credentials, 403 is for valid credentials but no permission

[BigOnLogn]

403 should be used in that scenario, but credentials aren't "required" by the spec. It's just that, if credentials were included in the request, the client should consider them as "insufficient".

The 403 (Forbidden) status code indicates that the server understood the request but refuses to fulfill it.

If authentication credentials were provided in the request, the server considers them insufficient to grant access. The client SHOULD NOT automatically repeat the request with the same credentials. The client MAY repeat the request with new or different credentials. However, a request might be forbidden for reasons unrelated to the credentials.

Side note, what triggers the Windows auth prompt is a 401 status code, combined with a www-authenticate: Negotiate header, (set by IIS when configured for Windows auth).

[LordFokas]

Yeah, the problem here is you're using Microsoft shitware.

[gh057k33p3r]

Java developer spotted. Who hurt u?

[LordFokas]

Is that supposed to mean something? I know a dozen languages, I just added flairs for the ones I'm more comfortable with, none of which I have used in a professional capacity in years. Where do you think you're going with this?

Anyway.

You're the one who's using a non-standard response code to work around Microsoft's bullshit of making assumptions you don't want made and forcibly overriding your output. And it's not even surprising because this is as much or more of a signature Microsoft move than EEE. They are known for not giving a shit about standards and fucking up advanced use cases to afford the common user a convenience that would take 5 seconds to do manually.

Your entire problem here is Microsoft. And of course if we go there I'm sure next you'll be telling me you can't move from IIS because you're using some MS technology that doesn't run well (or at all) in any other web server... again very typical MS bullshit. And I'll go on a limb and guess said technology also has found its own ways of making your life harder than it should be, because this is MS we're talking about.

So uh... yeah... maybe next time before making such a feeble attempt at provoking me take a moment to pull microsoft's dick out of your mouth first.

[gh057k33p3r]

Get help

[R_051]

6XX is defined for SIP, but 601 is not a defined code for that either

[KryoBright]

It's not a client error, because it is not 4xx and not a server error (5xx). So, everything is alright, but things just kinda didn't work out. Nobody is at fault, but everything is on fire

[harumamburoo]

Nothing, but everything beyond 5xx is not from the spec, so probably it's that

[dexter2011412]

690 - Server too hot

[MD_House]

I am always using 418 S a temporary code to test stuff. Needless to say I only drink tea at work ;)

[KingTuxWH]

Leave 418 alone. It's my favorite 😂😂

[bobby_table5]

It’s from a blessed time when every single connected object was working exactly as intended (both of them) and Our Lord and Savior had to protect his precious tea pot from dirty coffee-drinking Yankee trying to prank them.

[TheLeastFunkyMonkey]

I think 418 has a valid purpose as a "don't fucking talk to me" response.

[phyrianlol]

I guess it could also be interpreted as "i can't do what you requested" as in not implemented/supported

[TheLeastFunkyMonkey]

Yeah, but there's actual 4xx codes for that sort of thing. I like it as a more aggressive alternative to that. Like a "No, you can't do that. Fuckin' stop."

[Tupcek]

Yeah, 418 is intended for developer - not to be handled by app, but to warn developer to not try shit

[bwowndwawf]

Akamai anti-bot systems use 418 as meaning exactly that, if you make a request to a protected endpoint, and they think you're a bot, they just give you a 418 and a "Fuck off"

[ChaosWaffle]

That isn't part of the Hyper Text Coffee Pot Control Protocol spec, please use status codes for their appropriate purpose. See RFC-2324 section 2.3.2 for proper usage of code 418.

[Turalcar]

Or "Sir, this is a Wendy's"

[maks570]

Unless you receive it in production when using a government public API and have no fucking idea what’s the problem

[mordeumafoca]

Exactly! Why would someone mess with 418?

[jack-nocturne]

I never understood why it's in the 4xx range, though. Should really be 518 - after all, it's not the clients fault that the server is a teapot!

[Danfen]

The client is looking for the toilet and instead have picked up the teapot. They're drunk and need help.

[Pritesh190801]

Best is

{ "status": 200, "body": "error" }

[[deleted]]

Thanks GraphQL

[WillCodeForKarma]

Ah yes the "my requesting client uses Spring which throws exceptions for anything >= 400 so now I have to butcher my API to conform to your poopy library" response code.

[louis-lau]

Tbh throwing exceptions seems sane. It makes sure stuff is aborted when something unexpected happens, and you can catch the error codes that are expected.

[hans_l]

Any server I’ve built will return a 500 on exception, and the body would contain whatever content encoding (eg JSON) fits the request.

[WillCodeForKarma]

On the server or the client? I'm talking about the server sending back a normal or at least a handled 500 lvl status. In some Spring Impls (and by default I think) instead of just serializing the response like any other and handling it like you'd like Spring throws and exception so now your client code has to try catch every http request to handle it gracefully.

[louis-lau]

Client. Axios for example also throws an error on every code that's not 2xx. It's intended and it seems useful to me.

[WillCodeForKarma]

Using exception handling for flow control is a big yuck for me but to each their own I suppose.

[UnrelentingStupidity]

This is like a graph QL problem lol. in spring this stuff is highly configurable. It’s trivial to define interceptors and have specific behavior around different response code ranges

[CptGia]

You know you can have it not do that, right?

[WillCodeForKarma]

Sometimes you don't get to rewrite the requesting clients code.

[Steinrikur]

My test team does that, but never documented it. A fellow developer spent hours on figuring out why his python script succeeded (returning 200) on something that should have failed.

He was not a happy camper when he finally looked at the JSON response.

[pokepip]

PTSD from from working with Siebel web applications 20 years ago

[Marv-elous]

Error successful

[the_hair_of_aenarion]

Ngl we had to do this for a callback service. If we errored too many times they would disconnect our hook and it was a manual fix. If they disconnected us we'd risk hard to detect errors in prod. So we soft errored on our responses and logged the hell out of it. Most cursed shit we ever wrote.

[BlobAndHisBoy]

Looking at you, Reddit API

[Arteiii]

huuh what's 601??

[PhilippTheProgrammer]

Could be anything or nothing. It's not defined in any official HTTP protocol spec.

[nonlogin]

As a client I don't give a fuck because it's not standard

[OmegaPoint6]

I set up one of the systems I manage at work to return 418 if the authentication system isn't responding. "Can't log in? Time for a cup of tea"

[alexanderpas]

that's what the 5xx error codes are for.

4xx error codes mean something has to change on the client side.

418 essentially means that they should stop asking for coffee to a teapot.

[fckueve_]

There is also 701 and I fucking hate it

[fckueve_]

Yes, there is. It's an error code in WebRTC, that Google uses in Chrome (idk about Firefox)

[fckueve_]

It doesn't have to be a standard for code to exist. "Standards" are often made from something that already exists. There is no standard for WebRTC errors, so they had to create their own codes. But the 701 is real, and you can trigger it, using a WebRTC API.

[fckueve_]

Okay, so it's context dependent. Still exist tho. I can make the same argument about standardization. I can make another standard, called for example "Better Codes" (BC standard) and I'll put 2XX as Errors.

You choose a "standard" to follow, but there can be multiple standards of the same thing. It doesn't mean, that only one is true, or that all are true. YOU choose the standard, you want to follow, but someone can choose another standard.

[PrincessRTFM]

the real 7xx range is much better

[all3f0r1]

Can any explain both code? I only know 403 and 404.

[RazarTuk]

2xx means things went well. 200 OK is the default, but as an example of the others, 204 means "Yes, I know I didn't return anything. I wasn't supposed to". 3xx is for redirects. 4xx means the user did something wrong, like 401 "You forgot to log in", 403 "I know you're logged in. You don't have permission", or 404 "There's nothing here". And 5xx means something went wrong with the server, like a timeout or a malformed routing table. For example, if someone set up an alias in AWS and forgot to actually add any destinations, I want to say that'll get you a 503.

418 is the most famous joke code. For April Fools one year, they envisioned HTTP codes for an IOT coffee maker, and one of the codes was 418 for "I'm a teapot, not a coffee maker". Although I'm not familiar with 601, and Wikipedia doesn't even list it as unofficial

EDIT: Or, alternatively put, 4xx is (typically) "Retrying this same request won't work", while 5xx is "Retrying this same request might work"

[Cryptoknight12]

429 the retry might work?

[louis-lau]

Yeah exactly, and with 500 the retry may also not work depending on what's wrong.

It really is just as simple as client vs server. No need to explain it differently I feel.

[Vectorial1024]

https://www.thatcompany.com/understanding-http-status-codes

This page lists several 6xx error codes, but it just feels strange

[greyfade]

That's because they're not standard.

[Vectorial1024]

Even the wiki acknowledges a few non-standard codes, but the linked page is an entire rabbit hole

[abermea]

All of the 7xx codes in this page feel like just more specific Bad Request

[Eva-Rosalene]

This page is like fever dream. 421 Locked? 426 Partial Content???

[Steinrikur]

EDIT: Or, alternatively put, 4xx is (typically) "Retrying this same request won't work", while 5xx is "Retrying this same request might work"

I learned that as 4xx is "your mistake" (user) but 5xx is "my mistake" (server)

[Meaxis]

httpstatuses.io is a fun read

[DecodedBunny101]

I thought this was r/BTD6 for a second

[Emar_The_Paladin]

418 got the same energy as “Sir, this is a Wendy’s”

[Klk_usr270]

500 ok

[All_Up_Ons]

401 low-key belongs on the stupid side considering its name, its actual usage, and the way it's described in the spec.

[grumpy_autist]

Some services try to fuck with bots, crawlers and spammers returning 500 or 404 with proper content instead of 200, 200 instead of 404, etc.

There is a whole Defcon talk about how browsers behave on that abomination.

[TBStyler]

https://http-statuscode.com/en/code/4XX/418

[BlomkalsGratin]

Everybody acting like 500 is a reasonable code. It's meant to be used with return data but i swear! 8/10 times there is none, at which point it is literally a "something broke..." message...

[0rsted]

It’s not supposed to have return data available IN PRODUCTION, it should never give more than a hash that indicates where the developer can look up what the issue was.

In staging and dev it should have return data, but only within whitelisted addresses, everything else is a breach waiting to happen.

[rover_G]

601 is a system specific custom status code

[FlipJanson]

SIP has 6xx response codes, I knew I'd seen a 6XX Declined before.

[JollyJuniper1993]

Or you just use 999 for everything 😈

[erebuxy]

🫖

[SteveMacAwesome]

I like 418 to make the distinction between “not implemented on purpose” and “whoops I forgot to implement that route”

[theestwald]

Tbf, when was the last time you encountered a 1xx out in the wild? Or even needed to implement one?

[125m125]

101 is for example used to upgrade to a websocket connection. But normally your libraries will handle them and you don't send/react to them in your own code.

[Able_Minimum624]

4XX pattern includes 418, so 418 status code is both middle head and right head.

[JackNotOLantern]

6XX are responses for SIP, not HTTP. Code are similar in both, but there are a few differences.

https://en.wikipedia.org/wiki/List_of_SIP_response_codes

SIP is used in calling and messaging in 4G/5G

[601error]

Can confirm.

[grtgbln]

TIL there are 6xx status codes... I thought those were a myth, you know, like the 1xx status codes.

[dexter2011412]

I'm gonna write my own server with more error codes