Configuring CORS

This section describes how to use CORS in HTML5 to implement cross-origin access.


Static website hosting has been configured. For details, see Configuring Static Website Hosting.


  1. In the bucket list, click the bucket you want to operate. The Overview page is displayed.

  2. In the Basic Configurations area, click CORS Rules. The CORS Rules page is displayed.

    Alternatively, you can choose Basic Configurations > CORS Rules in the navigation pane.

  3. Click Create. The Create CORS Rule dialog box is displayed. See Figure 1 for details.


    A bucket can have a maximum of 100 CORS rules configured.

    **Figure 1** Creating a CORS rule

    Figure 1 Creating a CORS rule

  4. In the CORS Rule dialog box, configure Allowed Origin, Allowed Method, Allowed Header, Exposed Header, and Cache Duration (s).

    Table 1 Parameters in CORS rules



    Allowed Origin


    Specifies the origins from which requests can access the bucket.

    Multiple matching rules are allowed. One rule occupies one line, and allows one wildcard character (*) at most. An example is given as follows:

    Allowed Method


    Specifies the allowed request methods for buckets and objects.

    The methods include Get, Post, Put, Delete, and Head.

    Allowed Header


    Specifies the allowed headers in cross-origin requests.

    Only CORS requests matching the allowed headers are valid.

    You can enter multiple allowed headers (one per line) and each line can contain one wildcard character (*) at most. Spaces and special characters including &:< are not allowed.

    Exposed Header


    Specifies the exposed headers in CORS responses, providing additional information for clients.

    By default, a browser can access only headers Content-Length and Content-Type. If the browser wants to access other headers, you need to configure those headers in this parameter.

    You can enter multiple exposed headers (one per line). Spaces and special characters including *&:< are not allowed.

    Cache Duration (s)


    Specifies the duration that your browser can cache CORS responses, expressed in seconds. The default value is 100.

  5. Click OK.

    Message "The CORS rule created successfully." is displayed. The CORS configuration takes effect within two minutes.

    After CORS is successfully configured, only the addresses specified in Allowed Origin can access a bucket in OBS using the methods specified in Allowed Method. For example, you can configure CORS parameters for bucket testbucket as follows:

    • Allowed Origin:

    • Allowed Method: GET

    • Allowed Header: *

    • Exposed Header: *

    • Cache Duration (s): 100

    By doing so, OBS only allows GET requests from to access bucket testbucket, without restrictions on request headers. The client can cache CORS responses for 100 seconds.