I have replied to them with scripts, curl commands, and Swagger docs (PROVIDED TO SUPPORT THEIR API), everything that could possibly indicate there's a bug. Regardless, they refuse to escalate me to level 1 support because "We cant reproduce the issue in a dev environment"

Well of course you can't reproduce it in a dev environment otherwise you'd have caught this in your unit tests. We have a genuine issue on our hands and you couldnt give less of a shit about it, or even understand less than half of it. I literally gave them a script to use and they replied back with this:

"I cannot replicate the error, but for a resource ID that doesnt exist it throws an HTTP 500 error"

YOUR APP... throws a 500... for a resource NOT FOUND?????????!!!!!!!!!! That is the exact OPPOSITE of spec, in fact some might call it a MISUSE OF RESTFUL APIs... maybe even HTTP PROTOCOL ITSELF.

I'm done with IBM, I'm done with their support, I'm done with their product, and I'm DONE playing TELEPHONE with FIRST TIER SUPPORT while we pay $250,000/year for SHITTY, UNRELENTING RAPE OF MY INTELLECT.

  • 24
    People who don't use HTTP status codes correctly are the worst.
  • 12
    Some of their products use codes above 500 and/or in the 900 area.

    Yeah we have a special case, just for them...
  • 0
  • 0
    scenes full of awful perversions rise in my mind
  • 14
    I once saw an API that returned the status code of 500 with a hardcoded (plaintext) response "ok". I shit you not.
  • 2
    @010001111 900 level errors break the simulation, must avoid those to protect the universe
  • 2
    @mvelebit That's insane. Who on earth thought that was acceptable?? It's not like the status code standard is new.
  • 4

    Is what we call them in our shop.
  • 1
    @jallman112 I'm stealing this haha thats great!
  • 1
    The REST service which I am using in a mobile app is sometimes returning 500 with some html content.

    I‘d be happy to have 900+ status code instead of this useless shit.
  • 2
    Noted : Avoid IBM like the plague
  • 1
    I used to work at a company which was acquired by IBM.
    Once they onboarded 1000+ clients within a day (we initially had <250), this was an almost weekly exercise.
    Some nitwit sitting in a remote office, with no idea how to configure our solution was the 'onsite expert' deployed there by IBM. They would basically be on a call with us trying to learn the software first hand, over a call, on a live deployment issue.
    3 years of that shit, and I had to take a break from life, the universe, and everything.
Add Comment