• This is Microsoft.
  • He returns Webhook success with a code 200 and plaintext 1.
  • He returns Webhook failure with a code 200 and a string tells its endpoint returned error 400.
  • the string didn’t tell what exactly the error.
  • Don’t be like Microsoft.

EDIT: Got a few details wrong since this happens a few months ago and this meme used to be on r/ProgrammerHumor. Also the proof:

  • barrage4u@lemmy.world
    331·
    1 year ago

    It’s hard when you hit an endpoint that hits another endpoint, because technically the first request IS a 200. No right or wrong way as long as they are consistent and document it clearly imo

  • marcos@lemmy.world
    13·
    1 year ago

    The quality of Microsoft APIs is legendary… if you just take a minute to study win32, you will be always glad that those webserver responses are the kind of shit you have to deal with.

    But to be fair, this looks exactly like a well designed API that somebody pushed behind a corporate firewall.

  • jagoan@lemmy.world
    2·
    1 year ago

    Yeah, typical on .net too. I just have a middleware and turn it into proper REST. Though all the error messages are usually like ‘something went wrong’.

  • UncommonBagOfLoot@lemmy.world
    1·
    1 year ago

    Wait, do you know if this still happens?

    I have a ticket in our backlog to investigate similar issue with Teams Webhook reporting success but not posting anything.

    None of us wanted to look at it so been in our backlog for a whilr

    • bane_killgrind@lemmy.ml
      1·
      1 year ago

      There’s a video somewhere by someone… Returning a blank document instead of an error code is sometimes a QoS decision. Clients won’t make a new request without the user intervention, so whatever resource that’s bottlenecked has time to catch up

  • flashgnash@lemm.ee
    1·
    1 year ago

    Working with Microsoft’s APIs is akin to trying to navigate a maze of barbed wire with a blindfold on