5
slrpnk.net not giving file size in headers
(slrpnk.net)
That accept-ranges: bytes header smells like a rabbithole that might have clues. It could also just be a bug, I’m not sure
Can you please confirm if other Lemmy instances behave the same way?
Appears so.
$ curl -i https://lemmy.ml/pictrs/image/8122d979-9b5a-4c2b-bced-a685a1e05030.jpeg
HTTP/2 200
server: nginx
date: Mon, 22 Jan 2024 11:55:17 GMT
content-type: image/jpeg
vary: Origin, Access-Control-Request-Method, Access-Control-Request-Headers
last-modified: Tue, 24 Oct 2023 08:09:58 GMT
cache-control: public, max-age=604800, immutable
access-control-expose-headers: accept-ranges, date, last-modified, content-type, cache-control, transfer-encoding
accept-ranges: bytes
referrer-policy: same-origin
x-content-type-options: nosniff
x-frame-options: DENY
x-xss-protection: 1; mode=block
My guess is that this is a result of the Lemmy back end proxying all images served by pict-rs.
Personally I think that is a bad design choice, but I am not deep enough into the topic to really have a qualified opinion on it.
Here we can discuss anything about this Lemmy instance/server itself.
Our XMPP support chat: Movim or XMPP client.