It's not supposed to, that's expected

location / {
        if ($request_method = 'OPTIONS') {
    add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS';
    add_header 'Access-Control-Allow-Headers' 'DNT,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Range';                                                                                                  
    add_header 'Access-Control-Allow-Credentials' 'true';

    add_header 'Access-Control-Allow-Origin' $http_origin;
    add_header 'Access-Control-Max-Age' 1728000;
    add_header 'Content-Type' 'text/plain; charset=utf-8';
    add_header 'Content-Length' 0;
    return 204;
}

This configuration in nginx solved the issue for us on a local setup

Explicitly allow the Origin you need.

*

has caveats for authenticated requests and is not the same as specifying exact origins.

That's not really how CORS is supposed to work - a

204

with appropriate headers is returned if your request matches your CORS configuration, and is only returned in response to a request with the right headers rather than always responding to an

OPTIONS

request.

Without having the URL of the bucket, it's hard to test. You can replicate the request w/ curl and see the response body/headers.

we setting up an expamle

That means in the configuration of my web app I have to set region:auto?

We have a preview of the issue setup https://hls-js.netlify.app/demo/ - here is a hsl player https://vcdn.cf.all1.leap-gaming.com/videotest/res/t/Big_Buck_Bunny_first_23_seconds_1080p.m3u8 this is the link

Seems fine to me?

yeah, try firefox now

the video works fine for me in firefox

I see this while trying to play it

weird I don't

oh - it defaults to a different video url, I see

now it's broken for me too

its .MP4 not .TS. strange

I get this

It has all the parts and encoding is the same. Max just didn't rename it properly

Getting this cors error while loading a video that I previoulsy uploaded and sent to bucket

Any hint?

You haven't set up a CORS policy for the bucket / file.

Well I did, but seems that is not working

Have you tried using a custom domain? I don't think you can use the *.r2.cloudflarestorage.com if you have not presigned the URL.

See: https://developers.cloudflare.com/r2/learning/cors

This is my cors plicy

As you've specified "*" as a allowed origin you could remove the other ones. But this should not matter now