• Mak'@pawb.social
    link
    fedilink
    English
    arrow-up
    28
    arrow-down
    2
    ·
    7 days ago

    …HTTP is a high level application protocol and its errors are supposed to be around access to resources…

    I’ve had fellow developers fight me on this point, in much the same way as your parent post.

    “If you return a 404 for a record not found, how will I know I have the right endpoint?”

    You’ll know you have the right endpoint because I advertised it—in Open API, in docs, etc.

    “But, if /users/123 returns a 404, does that mean that the endpoint can’t be found or the record can’t be found?”

    Doesn’t matter. That resource doesn’t exist. So, act appropriately.

    • boonhet@lemm.ee
      link
      fedilink
      arrow-up
      9
      ·
      7 days ago

      Standardize a response body across your APIs that specifies the cause of the non-2xx response. Have an enum per API/service for causes. Include them in the API doc.

      If anyone still doesn’t get it, quietly dispose of them at your friend’s pig farm.

    • Takumidesh@lemmy.world
      link
      fedilink
      arrow-up
      4
      ·
      6 days ago

      It’s not like you can’t return a body with the 404 that specifies that the user itself is not found versus the ending being wrong.