Open JustaPeriod opened 1 year ago
I found that trying to view it in firefox actually gave me something at least, unlike chrome.
<html><head><meta name="viewport" content="width=device-width; height=device-height;"><link rel="stylesheet" href="resource://content-accessible/ImageDocument.css"><link rel="stylesheet" href="resource://content-accessible/TopLevelImageDocument.css"><title>raw ( Image)</title></head><body><img src="https://example.com/xahO4/zERUJOfO85.png/raw" alt="The image “https://example.com/xahO4/zERUJOfO85.png/raw” cannot be displayed because it contains errors."></body></html>
If I add ?width=500 so it actually loads, here's what I get:
<html><head><meta name="viewport" content="width=device-width; height=device-height;"><link rel="stylesheet" href="resource://content-accessible/ImageDocument.css"><link rel="stylesheet" href="resource://content-accessible/TopLevelImageDocument.css"><title>scaled-2023-07-31_09-19-23.png (PNG Image, 500 × 217 pixels)</title></head><body><img src="https://example.com/xahO4/zERUJOfO85.png/raw?width=500" alt="https://example.com/xahO4/zERUJOfO85.png/raw?width=500" class="transparent"></body></html>
I'm experiencing the same problem with S3 and SQLite. Kinda weird, but I don't get any errors in the logs.
Actually. When reading the nginx logs I saw something:
2023/09/16 16:51:10 [error] 267#267: *1 upstream sent invalid "Content-Length" header: "Content-Length: " while reading response header from upstream, client: 10.42.0.11, server: _, request: "GET /HAbU8/cUxAFelu41.png/raw HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "<domain>", referrer: "https://<domain>/HAbU8/cUxAFelu41.png"
2023/09/16 16:51:24 [error] 267#267: *1 upstream sent invalid "Content-Length" header: "Content-Length: " while reading response header from upstream, client: 10.42.0.11, server: _, request: "GET /HAbU8/cUxAFelu41.png/raw HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "<domain>", referrer: "https://<domain>/HAbU8/cUxAFelu41.png"
2023/09/16 16:52:54 [error] 270#270: *10 upstream sent invalid "Content-Length" header: "Content-Length: " while reading response header from upstream, client: 10.42.0.11, server: _, request: "GET /HAbU8/cUxAFelu41.png/raw HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "<domain>", referrer: "https://<domain>/HAbU8/cUxAFelu41.png"
Having the same issue, is there any update on this?
Duplicate of #536
has anyone been able to fix this?
System Info
Describe the bug Files uploaded to s3 buckets are not viewable raw. The files upload just fine, and are viewable and downloadable from the bucket or via a different tool, but do not load on xbackbone with /raw. In fact, it seems there is literally no header received when viewing files /raw. I get a completely blank page with no information to inspect in my browser.
Thumbnails display fine though. If I add ?width=500 or similar after /raw the images load fine. And local storage works absolutely fine, files display correctly.
I cannot download other files such as zips or videos. Any file you try to download saves as an empty file with 0 bytes downloaded. Seems identical to what someone else faced in #311
I have tried three different S3 compatible buckets with the exact same results: IDrive E2, Fybe, and Wasabi.
To Reproduce Upload file via website or sharex and visit page.
Expected behavior The files appear neither on the normal link or the /raw link. If I take the raw link and add ?width=1000 to the end or similar, it then displays fine.
Screenshots You can see the image upload is broken here: But the thumbnail works just fine here:
Logs XBackBone Log viewing images (no error, but no image loads):
Here's the XBackBone Log after trying to watch a video (url replaced). Probably because it's trying to load an empty stream?
No apache error log.
Apache Access Log for the image: