This has Content-Type: application/octet-stream, resulting in failure to embed on many platforms and causing unwanted downloads when viewed directly.
Asaf apparently fixed this content type issue a while ago, but old assets still have the wrong values. Could we write a script that fixes this for old assets? We would need to figure out when Asaf fixed the bug and how we now determine content types, and then figure out how to update all the media in place without ruining URLs.
For example: https://hmn-assets-2.ams3.cdn.digitaloceanspaces.com/0577107f-19e0-4ec8-b7f8-46aaa9261f2a/Screenshot_2021-10-03_212448.png
This has `Content-Type: application/octet-stream`, resulting in failure to embed on many platforms and causing unwanted downloads when viewed directly.
Asaf apparently fixed this content type issue a while ago, but old assets still have the wrong values. Could we write a script that fixes this for old assets? We would need to figure out when Asaf fixed the bug and how we now determine content types, and then figure out how to update all the media in place without ruining URLs.
For example: https://hmn-assets-2.ams3.cdn.digitaloceanspaces.com/0577107f-19e0-4ec8-b7f8-46aaa9261f2a/Screenshot_2021-10-03_212448.png
This has
Content-Type: application/octet-stream
, resulting in failure to embed on many platforms and causing unwanted downloads when viewed directly.Asaf apparently fixed this content type issue a while ago, but old assets still have the wrong values. Could we write a script that fixes this for old assets? We would need to figure out when Asaf fixed the bug and how we now determine content types, and then figure out how to update all the media in place without ruining URLs.