I’m still sometimes getting broken pictures that are not supposed to be broken

  • loathesome dongeaterA
    link
    fedilink
    English
    arrow-up
    8
    ·
    2 months ago

    I am assuming by server you mean pict-rs. Is there a reason you think why pict-rs assumes valid requests are malformed?

    • The Free PenguinOP
      link
      fedilink
      arrow-up
      6
      ·
      edit-2
      2 months ago

      GET
      https://lemmygrad.ml/pictrs/image/219c5656-9cb1-4f85-af6d-01581f997dd6.png

      Accept
      text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,/;q=0.8
      Accept-Encoding
      gzip, deflate, br
      Accept-Language
      en-US,en;q=0.5
      Connection
      keep-alive
      Cookie
      <Cookie censored>
      Host
      lemmygrad.ml
      Referer
      https://lemmygrad.ml/\ Sec-Fetch-Dest
      document
      Sec-Fetch-Mode
      navigate
      Sec-Fetch-Site
      same-origin
      Sec-Fetch-User
      ?1
      Upgrade-Insecure-Requests
      1
      User-Agent
      Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/115.0

      Here are the request headers. This is a perfectly valid requests. Please change your server settings to process these requests rather than throwing 400s.

      • davel
        link
        fedilink
        English
        arrow-up
        3
        ·
        edit-2
        2 months ago

        Huh?

        $ curl -o /dev/null -s -w "%{http_code}\n" https://lemmygrad.ml/pictrs/image/219c5656-9cb1-4f85-af6d-01581f997dd6.png
        200
        $
        

        It looks like your Accept is lacking image/png; maybe that’s the issue?