Apparently Wasabi was setting its own CORS headers and I was setting my own CORS headers in my proxy so all files were served with invalid double CORS headers which led to the new audio player not working in Chrome.

The headers situation should now be resolved although your browser will probably cache the wrong thing for a long time. What I'm saying is I think future uploads should play fine.

Follow

@Gargron CORS is such a PITA, even if it is needed :(

Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.