When an end user requests a business resource, you can add a custom header in the returned response message to implement cross-origin access.
As the HTTP header configuration is for a specified domain name, once the configuration takes effect, the configured header will be added to the response messages of user requests for any resource under this domain name. HTTP header configuration affects only response of the client (such as browser) rather than CDN node's caching behaviors.
Log in to the CDN Console, select Domain Management on the left sidebar, and click the domain name to enter its configuration page. You will find the response header configuration on the Advanced Configuration tab. It is disabled by default.
Toggle the switch and add HTTP header configuration. Currently, the following headers can be configured. You can also add custom headers:
General configuration: Content-Disposition
Content-Disposition is used to activate download in the browser and set the default filename of the downloaded resource. When the server sends a file to the client browser, if it is in a type supported by the browser, such as TXT or JPG, it will be directly opened in the browser by default. If you want to ask the user to save the file, you can configure the
Content-Disposition field to override the browser's default behavior. The common configuration is as follows:
General configuration: Content-Language
Content-Language specifies the language code used by the webpage. Common configurations are as follows:
Cross-origin configuration: Access-Control-Allow-Origin
Cross-origin access refers to a scenario where a resource under a domain name, such as
www.abc.com, initiates a request to another resource under another domain name, such as
www.def.com. As the resource domain names are different, cross-origin access will occur. Using different protocols or ports can cause cross-origin access. You need to add configuration related to cross-origin access in the response header to make the first resource get the desired data.
Access-Control-Allow-Originis used to solve the problem of cross-origin permissions of resources. Up to 10 values of origins allowed to access a resource can be configured. If a source request's host is in the configured domain name list, the corresponding value will be directly populated into the returned header. You can also set the wildcard "*" to allow all origins to access the resource.
|Match Mode||Origin Value||Description|
|Full match||*||If it is set to "*", the following header will be added to the response:
|Second-level wildcard domain name match||
If there are special ports, you need to enter the relevant information in the list. Arbitrary port match is not supported, and you must specify the ports.
Cross-origin configuration: Access-Control-Allow-Methods
Access-Control-Allow-Methods is used to specify the HTTP request methods allowed for cross-origin access. Multiple methods can be set as follows:
POST, GET, OPTIONS
Cross-origin configuration: Access-Control-Max-Age
Access-Control-Max-Age specifies the validity period of a preflight request.
For a non-simple cross-origin request, before the formal communication, an HTTP query request called "preflight request" needs to be made to check whether the cross-origin request is secure and acceptable. The following requests are considered as non-simple cross-origin requests:
POSTor is initiated by using
POSTwith a data type other than
application / x-www-form-urlencoded,
multipart / form-data, and
text / plain(such as
application / xmlor
text / xml).
Access-Control-Max-Ageis measured in seconds. Below is a configuration sample:
This indicates that no more preflight requests will be sent for the cross-domain access to this resource within 1,728,000 seconds (20 days).
Cross-origin configuration: Access-Control-Expose-Headers
Access-Control-Expose-Headers specifies which headers can be exposed to the client as part of the response. By default, the following six types of headers can be exposed to the client:
If you want the client to access other header information, you can use the following setting and separate multiple headers with ";".
This indicates that the client can access
You can add a custom header and customize
Currently, the following headers cannot be added:
Date Expires Content-Type Content-Encoding Content-Length Transfer-Encoding Cache-Control If-Modified-Since Last-Modified Connection Content-Range ETag Accept-Ranges Age Authentication-Info Proxy-Authenticate Retry-After Set-Cookie Vary WWW-Authenticate Content-Location Content-MD5 Content-Range Meter Allow Error
If multiple identical headers are added, the lower the position, the higher the priority, and the header below will overwrite the header above it.
You can toggle the HTTP header switch to disable this feature. When the switch is off, existing configurations will not take effect in the production environment.
If your domain name is configured for global acceleration, the response header configuration will take effect globally. This configuration does not distinguish between requests from Mainland China and from outside Mainland China.