Updated on 2026-07-27 GMT+08:00

AccessForbidden

CORS is not enabled for this bucket.

Error description

CORS is not enabled for this bucket.

Error cause

During cross-origin access, no CORS rule is configured for the bucket, and the CORS rule list is empty. As a result, the cross-origin access is rejected.

Handling suggestion

Configure CORS rules for the bucket on OBS Console or using APIs. For details, see Configuring CORS to Allow Cross-Origin Access to OBS.

This CORS request is not allowed. This is usually because the evalution of Origin, request method / Access-Control-Request-Method or Access-Control-Request-Headers are not whitelisted by the resource's CORS spec.

Error description

No bucket CORS rule matched.

Error cause

During cross-origin access, the requested origin, request method (Access-Control-Request-Method), or request headers (Access-Control-Request-Headers) do not match any CORS rule configured for the bucket.

Handling suggestion

Check the requested origin, request method, and request headers and ensure that they match a bucket CORS rule. To ensure access, contact the bucket administrator to add your origin, request method, and request headers to a CORS rule. For details, see Configuring CORS to Allow Cross-Origin Access to OBS.