Help Center/ Object Storage Service/ FAQs/ Buckets and Objects/ Why Is an Error Reported Even If CORS Has Been Configured?
Updated on 2022-09-27 GMT+08:00
View PDF

Why Is an Error Reported Even If CORS Has Been Configured?

  • Response headers are cached for the same URL. The result of the first simple request will be cached even if the request does not contain the CORS header. When the URL is accessed for the second time, the first response result is used and CORS is generated. This issue is caused by the browser mechanism.

    Use either of the following methods to try to resolve this issue:

    1. Add random parameters to the end of the requested resource URL. For example, 1.html?a=1 is displayed after a random parameter is added to 1.html.
    2. Set CacheControl to no-cache in the object metadata.
    3. Press Ctrl+Shift+Delete to clear the browser cache.
Parent topic: Buckets and Objects