What did you expect to happen? What happened instead?
When loading an archive that uses Flash (https://ysdn.info/archives/2009) Ruffle is unable to load https://www.apassionatecuriosity.com/float-quick.swf, a SWF file that does exist in the archive. This results in a 404, and Ruffle saying that: Access to fetch has likely been blocked by CORS policy.
CORS seems to be set up correctly for the site, all of the other archives function as expected in ReplayWeb.page, and all the archives are stored in Backblaze. This could very well be a configuration issue on my end, but we don't seem to document anything beyond what I've done. Finally, Ruffle also works properly when running the site locally which is doubly frustrating! Everything also works on ReplayWeb.page and in the ArchiveWeb.page app.
Clone the repo and follow the development instructions if you want to build the site locally and check that everything is embedded properly on your local machine.
None of the archive files are actually included in the repo and are all also loaded off Backblaze.
ReplayWeb.page Version
v2.1.1
What did you expect to happen? What happened instead?
When loading an archive that uses Flash (https://ysdn.info/archives/2009) Ruffle is unable to load
https://www.apassionatecuriosity.com/float-quick.swf
, a SWF file that does exist in the archive. This results in a 404, and Ruffle saying that: Access to fetch has likely been blocked by CORS policy.CORS seems to be set up correctly for the site, all of the other archives function as expected in ReplayWeb.page, and all the archives are stored in Backblaze. This could very well be a configuration issue on my end, but we don't seem to document anything beyond what I've done. Finally, Ruffle also works properly when running the site locally which is doubly frustrating! Everything also works on ReplayWeb.page and in the ArchiveWeb.page app.
Step-by-step reproduction instructions
Additional details
My Backblaze CORS config: