- Shipped
- August 23, 2026 at 12:53 AM UTC
- Author
- kamo
- Commit
- f0b5369
Every photo and video in a picture frame rendered as a broken image. The URL pointed at **************** I took that for a general imaging proxy — it speaks HTTP Range, which is what a video needs — and it is not one: it is the CHAT ATTACHMENT proxy. It binds a UUID, resolves a MediaObjImg, and authorises by chat-session membership. Frame media has an int64 id and no session, so nothing it asked for could ever be found. Reading the signature rather than the capability would have caught it in a minute. Media now comes from the frame's own endpoint, which authorises the way the rest of this feature does — the frame must be the member's, the media must be in that frame — so the URL takes both ids. The route forwards Range and relays 206 with Content-Range untouched, and passes response.body straight through instead of buffering, so a long video streams rather than being held whole in this process on its way to the browser.