230

Status code: 200
Content-Type: application/json
Body: {"error": true, "responseCode":400 }

Comments
  • 4
    Classic
  • 6
    So logical. I don't see anything wrong with it 😒
  • 4
    @DanijelH yeah it could be a status from another REST endpoint. 🤔
  • 1
    @diobert I was being sarcastic but yeah, we don't know the context of the story 😄
  • 3
    Haha I had exactly that when I joined a new company.

    This one's quite advanced though, it uses a boolean response for error and not a string "true" 😒
  • 1
    :@ our backend used to have this all the time. Instead of returning the correct result, it was stored in the object and the returning status code was 200. Drives you nuts when coding angular and error results keep taking the success path!
  • 1
    This fuckin happened to us today. A fuckin API that we were fuckin using in our fuckin application, fuckin did this fuckin blunder.
  • 1
    Hey at least the content type is ok...
  • 0
    My previous n+1 did the same shit on a previous project. The reason was "I don't want to mix network errors and application errors".

    After 20years, the guy didn't know that HTTP codes ARE application errors.

    Another story with the guy : https://devrant.com/rants/1440059/...
  • 5
    devRant API uses something like that. (Success = true/ false)
  • 0
    Found in the wild

    Status: 200
    Body: {"success": true, "message": "otp sent successfully to your number xxxxxxx", "otp": "1234"}
Your Job Suck?
Get a Better Job
Add Comment