this post was submitted on 17 Jul 2024
33 points (100.0% liked)

Comradeship // Freechat

2451 readers
101 users here now

Talk about whatever, respecting the rules established by Lemmygrad. Failing to comply with the rules will grant you a few warnings, insisting on breaking them will grant you a beautiful shiny banwall.

A community for comrades to chat and talk about whatever doesn't fit other communities

founded 4 years ago
MODERATORS
 

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

you are viewing a single comment's thread
view the rest of the comments
[–] thefreepenguinalt@lemmygrad.ml 8 points 1 year ago (1 children)

UPDATE: You need to tell your server to stop throwing 400s and just process the request, no matter how "malformed" it may think it is

[–] ksynwa@lemmygrad.ml 8 points 1 year ago (1 children)

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

[–] thefreepenguinalt@lemmygrad.ml 6 points 1 year ago* (last edited 1 year ago) (2 children)

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

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.

[–] ksynwa@lemmygrad.ml 7 points 1 year ago

Thanks. I'll look into it tomorrow.

[–] davel@lemmygrad.ml 3 points 1 year ago* (last edited 1 year 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?