CORS Problems

[mailing-lists <mailing-lists@xxxxxxxxx>]

Dear Cephers,

I am facing a Problem. I have updated our ceph cluster form 17.2.3 to 
17.2.7 last week and i've just gotten complains about a website that is 
not able to use s3 via CORS anymore. (GET works, PUT does not).

I am using cephadm and i have deployed 3 rgws + 2 ingress services.

The bucket shows:

aws s3api get-bucket-cors

{
    "CORSRules": [
        {
            "AllowedHeaders": [
                "*"
            ],
            "AllowedMethods": [
                "GET",
                "PUT"
            ],
            "AllowedOrigins": [
                "*"
            ],
            "ExposeHeaders": [
                "ETag",
                "Accept-Ranges",
                "Content-Encoding",
                "Content-Range"
            ]
        }
    ]
}

Which is supposed to be a working config (at least this was working 
until the update).

Cross-Origin Request Blocked: The Same Origin Policy disallows reading 
the remote resource at https:/EXAMPLE.com[.....] (Reason: CORS header 
‘Access-Control-Allow-Origin’ missing). Status code: 403.


I can not 100% say that the update is the culprit, but I haven't touched 
anything else and before the update it was working.

Did I miss an important change?


Best

inDane
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx