TRF.0052 Invalid CORS configurations.

Symptom

When you send a cross-origin request, the request is rejected. The possible reason is that the Cross-Origin Resource Sharing (CORS) policy is not correctly configured for the destination bucket, or the CORS configuration does not match the request.

Possible Causes

1. No CORS policy is configured for the bucket.
2. The allowed origin, method, and header parameters in the CORS configuration do not match the actual request.
3. The OPTIONS request sent by the client does not pass the CORS policy verification.

Solution

1. Check whether the request initiated by the client is a cross-domain request. This error occurs if the protocol, domain name, and port number in the request are different from those on the current page.
2. Ensure that CORS policies are configured for the destination bucket.
3. Ensure that the values of parameters such as AllowedOrigins, AllowedMethods, and AllowedHeaders in the CORS configuration are the same as those in the request.
4. Check the OPTIONS request response on the Network panel of the browser's developer tool to see if the correct CORS header information is returned.