Dev gets hold of me, says my service is down in QA. Works if he hits it locally, works via Postman, but via the QA app server it gives a 401.

I’m like, look, if it works everywhere else, there’s something wrong on your side in QA.

He insists, no, I must help him, and begins CCing all the managers telling them this system has been down for days.

So I eventually climb into his system, check the credentials they’re using in the QA environment, and sure enough, the password is wrong.

Besides the guy being a twat, why would it throw a 401 for a failed password... shouldn’t this be fixed to spew out proper error (then the twat would have not sunk you into shit).

@helloworld Why not? Seems like the correct status code to me.

@falloutghst Shit, I read it as 404 for some reason. Guess I am also a twat. 😬

@stillwater cc'ing everyone is very passive aggressive, but I've brought that back to bite people so many times with the following tactic.

Reply all:

Hi all,
Just to update everyone on this situation - I've investigated the issue with (dev) and we've discovered there was nothing wrong with the service, but the QA box was failing because it had been configured with an incorrect password. (dev) has now corrected the password on the QA box and everything is now working as normal.
Thanks!

@AlmondSauce *slow-clap* Well played.

Well CCing managers can be a dick move if it's right from the beginning, but when the other part does not move his fucking lazy ass I also CC them