• nothacking
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    1 year ago

    No, this is a lemmy issue. The API specification specifies a JSON response, and the server randomly provides HTML, this is a bug in the server. I agree that Jebora should retry in the case of a network failure (timeout, 4xx staus codes…) but it should not have to retry in a case of a server that is not folowing the standard.

    • Irisos@lemmy.umainfo.live
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Unfortunately this is a bug in the UI.

      Yes a 502 returns html (from nginx). But at that point, you should be validating the status code of the response instead of attempting a deserialization right away.

      This is a basic thing which according to other comments at least 4 apps are not doing and should definitely be present.

    • mc1472@lemmy.fmhy.ml
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      lemmy does not return 502 error codes because 502 means “bad gateway” and lemmy is not acting as a gateway, nginx is. An nginx sends the html. All apps should check the status code for codes like this one that don’t come from apps.