[ceph-users] Re: CORS Problems

5 Jun 2024

      Hi,

so there is a problem, alright!

I do not have a separate nginx proxy in front of my rgw/ingress. As far 
as I understand, the "ingress" service is only keepalived and haproxy. I 
am not sure how to strip the OPTIONS method within those containers...

I will probably just disable the redirect on the website and relay the 
upload for the time until it gets fixed.

Thank you for your input, this keeps me from spending more time 
investigating!

Best

inDane

On 05.06.24 18:13, Reid Guyett wrote:
...
Hi,
There is a bug with preflight on PUT requests: 
https://tracker.ceph.com/issues/64308.
We have worked around it by stripping the query parameters of OPTIONS 
requests to the RGWs.
Nginx proxy config:
if ($request_method = OPTIONS) {
    rewrite ^\/(.+)$ /$1? break;
}
Regards,
Reid
On Wed, Jun 5, 2024 at 12:10 PM mailing-lists 
<mailing-lists@indane.de> wrote:
OK, sorry for spam, apparently this hasn't been working for a month...
Forget this mail. Sorry!
On 05.06.24 17:41, mailing-lists wrote:
    > 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@ceph.io
    > To unsubscribe send an email to ceph-users-leave@ceph.io
    _______________________________________________
    ceph-users mailing list -- ceph-users@ceph.io
    To unsubscribe send an email to ceph-users-leave@ceph.io