Very cool! Will definitely take a look, I might have a good use case for this
Very cool! Will definitely take a look, I might have a good use case for this
npm i r2-player.js. There are no other projects in the npm registry using r2-player.js.





content-disposition properly. But if I use custom domain endpoint, it only delivery the file, the http header will not be generated like in the screenshot. If it is not a bug, could you tell me how to inject content-disposition in the right way?
Failed to load image: ${response.status} ${response.statusText}Failed to load image: ${error.message});cf-cache-statuscf-mitigatedcf-mitigated headercf-cache-status headerExposeHeaders is missing headers like ETagAllowedHeaders is missing headers like Authorization or Content-TypeAllowedMethods is missing methods like POST/PUT (you do not need to include OPTIONS)


cf-cache-statuscf-mitigatedcf-mitigated headercf-cache-status headerExposeHeaders is missing headers like ETagAllowedHeaders is missing headers like Authorization or Content-TypeAllowedMethods is missing methods like POST/PUT (you do not need to include OPTIONS)npm i r2-player.jscontent-dispositioncontent-dispositionFailed to load image: ${response.status} ${response.statusText}Failed to load image: ${error.message}