Origin Configuration
When you need to modify the origin-related configuration, this article will guide you on how to configure and points of attention.
Origin Site Configuration
The types of origin site supported by SurferCloudCDN include origin domain name, UFile domain, and IP.
- When there are multiple IPs for the origin site, the origin will be accessed in a round robin manner.
- If you have other needs that can't be met by the console, please contact technical support for configuration.
Origin Port Configuration
When making a back-to-origin request, it specifies the port to which the request is made.
| Port | Description |
|---|---|
| 80 port/443 port | Back-to-origin requests will return to the 80 or 443 port via HTTP or HTTPS protocols. |
| Custom Port | Customize the back-to-origin port, which can be specified through configuration. Only when the protocol is HTTP can the custom port be specified; if the protocol is HTTPS, the back-to-origin port can only be 443 |
Origin HOST Configuration
The back-to-origin HOST refers to the specific site that the CDN node accesses the origin site during the back-to-origin process.
| Origin HOST | Description |
|---|---|
| Acceleration Domain | By default, the back-to-origin HOST is the acceleration domain. |
| Origin Domain | When the origin is UFile, the back-to-origin HOST needs to be specified as origin domain name, otherwise the back-to-origin process will fail. |
| Custom Domain | Custom back-to-origin HOST. When the origin site has multiple domains or sites, you need to customize the domain name and specify the specific back-to-origin HOST. |
Origin Protocol Configuration
Specify HTTP or HTTPS protocol for back-to-origin requests.
| Origin Protocol | Description |
|---|---|
| HTTP Protocol | The back-to-origin request is made via the HTTP protocol. The default is the HTTP protocol. |
| HTTPS Protocol | The back-to-origin request is made via the HTTPS protocol. The origin site needs to support the 443 port. |
301/302 Redirection
When the back-to-origin request returns a 301/302 status code, the node will directly request the specified address for resources.
Operation steps:
- Enter the UCDN product console domain management page and select the domain that needs configuration.
- Enter the domain configuration details page, choose domain configuration->basic settings->back-to-origin settings, and make a back-to-origin related configuration.
- Modify the origin site, modify the back-to-origin HOST, back-to-origin port, back-to-origin protocol, etc.
After the configuration modification is complete, you must click confirm configuration to successfully modify the configuration.
Configure the origin site as US3 domain
- You need to create a storage space in US3, the space type is public space
- Click domaing management, enter the bucket domain management page, and click bind custom domain; the custom domain is filled in with the domain that needs to be accelerated in CDN, and select CDN acceleration as yes
- After clicking confirm, you will be transferred to the CDN configuration page, at this time the system has automatically filled in the acceleration domain name and origin site information, after confirming other configurations, you can click confirm to complete the CDN domain addition.
Note: In domain settings, the back-to-origin HOST needs to be configured as: follow acceleration domain name (default), otherwise US3 will not recognize the CDN back-to-origin traffic as CDN back-to-origin outbound traffic and charge (it will recognize it as external network outbound traffic for billing).
- After the confirmation, the new domain is successful, the page will be directed to the CDN domain management list, after the review and issue are completed, switching the domain name CNAME can complete CDN acceleration.
- The corresponding US3 custom domain will also add corresponding records in response
- If the storage space already exists, when configuring the business domain in the CDN, if the origin is US3's domain, US3 will automatically generate the corresponding business domain in the custom domain.
