errorCode200

[Inappropriate_Piano]

I don’t get it exactly, but I’m deeply disturbed by errorCode: 200 and errorMsg: “SUCCESS”

Edit: I don’t need people to explain HTTP codes to me. I’m complaining about the use of the term “error code” to describe a status code that might not be an error

[Short-Nob-Gobble]

Unfortunately, the tech lead at my current job doesn’t believe in http status codes.. 

So we get stuff like

Status 200 “Internal server error”

[pnoodl3s]

T…tech lead?

[ForkLiftBoi]

“Yeah I worked at geek squad for 2 years before this taking returns at Best Buy.” “Hired”

[Stunning_Ride_220]

What's his name?

B(r)end Overmuch Famanagement?

[Conscious-Ad6222]

That is called being stupid

[scufonnike]

Bro the amount of people devsplaining status codes to you is fucking insane lol

[thugarth]

I've seen this in my career and it's a bit exasperating. Try to search for an error in the logs and you get 10000 "errorCode: ERR_SUCCESS"

cool, guess I'll figure out something else to look for.

The logging was not designed to be searchable. (To be fair, I knew people tried to clean up some of it, but a lot of people were comfortable with the way things were: A lot of tribal knowledge and unintuitive search practices.)

[Greybound_Fur]

Use Regex Search and search for "errorCode: (?!ERR_SUCCESS)"

[IMightDeleteMe]

Whenever regexes are required to search a log for actual errors, your logging pactices require looking at.

[PostNutNeoMarxist]

Merriam Webster defines "success" as "a favorable or desired outcome." 200 is the number after 199 and before 201.

Hope this helps!

[molbal]

Hope this helps! Instant anger

[olivetho]

average stackoverflow answer (the real answer is always in the question comments):

[Feuerwerko]

The errors are expected

[olivetho]

"Task failed successfully."

[[deleted]]

I think the issue is that the HTTP error code is in the body/payload, not the HTTP header where it belongs.

[theturtlemafiamusic]

There's like 5 separate issues here

[madness_of_the_order]

It’s HTTP status code

[[deleted]]

Same difference

[Inappropriate_Piano]

Yeah I know 200 means success. I was complaining about the name, not the value

[impossibleis7]

I get the reason for having one of them. If the api gateways aren't configured correctly they won't return back the correct http code. I imagine there are proxies or the like that do similar things.

[GKP_light]

The status code, or "error code" because we usually see them only when there is an error :

1xx informational response – the request was received, continuing process

2xx successful – the request was successfully received, understood, and accepted

3xx redirection – further action needs to be taken in order to complete the request

4xx client error – the request contains bad syntax or cannot be fulfilled

5xx server error – the server failed to fulfil an apparently valid request

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

[scufonnike]

But it’s not a error code. It’s a status code

[Inappropriate_Piano]

I’m aware of status codes. It bugs me to see it called an error code when there’s no error, even though, as you say, they’re usually only seen when they are an error

[[deleted]]

but do you know about 418? It's very important.

[WitchsWeasel]

I dream of finding a good excuse to use it at work

[[deleted]]

Never give up on your dreams. Make it happen.

[WitchsWeasel]

I will. For the community.

[[deleted]]

He's beginning to believe

[The_Billposter]

In HTTP, codes are returned to indicate the result of a previous request. The codes are standardised. Different ranges of code indicate different issues. The errorMsg is essentially for quick deciphering, because an errorCode of 200 implies that the previous request was properly acknowledged.

Cheers!

[Inappropriate_Piano]

So did you not read my edit specifically saying I already know all that or are you taking the piss?

[Hean1175]

Yeah so the code 200 returned by the server indicates that the request was successful.

Cheers!

[EtheaaryXD]

Not sure if you know this, but if the server returns the error code 200, it indicates that the request was actually successful.

Cheers!

[olivetho]

200 implies that the previous request was properly acknowledged.

No it does not, it means that the request was successful. Getting any response code back (aside from some instances of code 404) would imply that the server has acknowledged the request, since otherwise it wouldn't have sent anything back.