Security CDN
Overview
Speed & Cache provides content delivery acceleration services for application-layer protocols such as HTTP/HTTPS. It is particularly well-suited for websites, applications, and similar content. Through a wide range of configurable capabilities—such as origin configuration, cache policy management, HTTPS acceleration, and content optimization—Speed & Cache helps significantly improve delivery efficiency and service stability. This enhances the end-user experience and empowers websites or applications to stand out in a competitive online environment.
Once you have integrated with Security CDN, you can customize and manage the following strategies:
| Category | Function | Use Case | Default Configuration |
|---|---|---|---|
| Origin Configuration | Follow 301/302 Redirects from Origin | When the edge node or proxy server receives a 301/302 redirect response from the origin server, it will follow the new URL itself instead of directly returning the redirect response to the client. | OFF |
| Origin Timeout | The maximum allowed waiting time for the edge node (such as CDN or reverse proxy server) to establish a TCP connection or complete the SSL handshake with the origin server. | Default 30 seconds | |
| Origin Request Timeout | The maximum time that an edge node waits for a response from the origin when initiating a request. If no response is received within this period, the request is considered an origin timeout. | Default 60 seconds | |
| Custom Origin HTTP Request Headers | Custom modification of HTTP headers carried by Security CDN edge nodes when making requests to the origin server. | OFF | |
| Origin URI Rewrite | When the requested resource directory in the origin request does not match the storage directory on the origin server, origin fetch failures may occur. Rewriting the origin URL can align the request URL with the origin server’s URL, improving origin fetch hit rate. | OFF | |
| Origin Detection | If multiple origin IPs exist, active probing can be performed to check the availability of the origin servers. | OFF | |
| Origin Health Check | When multiple origin IPs exist, if any origin IP exceeds the configured failure threshold within a specified time window, that IP will be temporarily disabled and not used as an origin target during the disable period. After the disable period ends, detection and origin fetch will automatically resume. | Origin Failure Threshold:30 items Failure Detection Interval:10 seconds Temporary IP Block Duration:30 seconds |
|
| Origin Protection | To prevent server overload caused by excessive origin fetch requests, set a limit on the number of origin requests within a specified time window. Requests exceeding this limit will be dropped. | OFF | |
| Range Request Configuration | When the edge node receives a client request with a Range header, it will issue the same range request to the origin server instead of downloading the entire resource. | OFF | |
| Enable Keep-Alive | Whether the edge node reuses existing TCP or HTTPS connections when making origin requests, instead of establishing a new connection for each request. This requires the origin server to support keep-alive. | ON | |
| Cache Management | Edge Cache TTL | Custom cache duration of resources on edge nodes. The default caching policy only applies to specified file types and HTTP status codes 200/206; 404 responses are cached for 10 seconds by default, and other status codes are not cached. | Follow origin Cache-Control, Use default policy if absent |
| Browser Cache TTL | Custom cache expiration time for client browsers. Browsers will load files from local cache before expiration, improving access speed and reducing redundant requests. | Follow origin Cache-Control | |
| Sort Query String | Enabling query string sorting causes the system to ignore the order of URL query parameters and cache resources based only on parameter names and values, thereby improving cache hit rate. | OFF | |
| Preserve/Lgnore Query String | When enabled, the system uses the URL query string as part of the cache key, meaning requests with the same URL but different query strings will generate different cached content. | Keep All | |
| Preserve/Lgnore Cookies | Users can customize which specific Cookie fields are included as part of the cache key to achieve more fine-grained caching strategies. | Ignore All | |
| Ignore Case | When cache ignore case is enabled, the system will treat URLs with different cases in the path and query parameters as the same resource for caching purposes. | Do Not Ignore | |
| Cache Rules | Cache rules configure caching strategies for static resources at edge nodes to improve access performance, reduce origin server load, and optimize end-user experience. You can flexibly control caching behavior by setting cache paths, file types, priorities, and cache durations according to business needs. | Refer to Security CDN Cache Rules | |
| HTTPS Configuration | HTTP to HTTPS Redirection | Automatically redirect client HTTP requests to HTTPS protocol to enhance data transmission security and prevent data tampering or interception during transit. | OFF Note:HTTPS certificate must be configured first |
| HTTP/2 | The new HTTP protocol version succeeding HTTP/1.1, providing faster website access speeds and smoother user experience. | OFF Note:HTTPS certificate must be configured first |
|
| HSTS | Force browsers to always use HTTPS encrypted connections to access the website, preventing downgrade attacks or hijacking on first visits or redirects from HTTPS to insecure HTTP. | OFF Note:HTTPS certificate must be configured first |
|
| OCSP Stapling | A technique to improve HTTPS website speed and security by letting the server prefetch and cache the SSL certificate status and directly provide it during handshake, avoiding client-side OCSP requests to the Certificate Authority. | OFF Note:HTTPS certificate must be configured first |
|
| Configure TLS Cipher Suites and Versions | TLS (Transport Layer Security) is the cornerstone of internet communication encryption, ensuring secure data transmission between users and servers. TLS protocol versions and cipher suites determine communication security levels and compatibility. | Minimum TLS version: TLSv1.2 Cipher Suites: All Available Cipher Suites Note:HTTPS certificate must be configured first |
|
| Performance Optimization | Gzip Compression | Significantly reduces the size of text-based resources (such as HTML, CSS, JavaScript, JSON) during transmission, speeding up page load times and reducing bandwidth usage. | ON |
| WebP Adaptive | Automatically selects whether to return WebP images based on browser support, balancing optimal performance and compatibility. | OFF | |
| Maximum File Upload Size | When accelerating and protecting websites via Security CDN, customers’ users may upload large files such as images, videos, or documents. To ensure website stability and security, Security CDN enforces upload size limits. | 100MB | |
| WebSocket | A protocol enabling full-duplex communication over a single TCP connection. Compared to traditional HTTP requests, WebSocket offers lower latency and higher communication efficiency, ideal for real-time scenarios like online chat, real-time data push, and game synchronization. | OFF | |
| Mobile Redirection | Automatically detect user device types (e.g., mobile phones, tablets) and redirect them to designated mobile pages, improving mobile user experience and page loading performance. | OFF | |
| Error Page Customization | Error Page Customization | For different error status codes, you can flexibly configure custom error pages to replace default error messages, providing users with a more friendly browsing experience. | OFF |
Need help? Contact our support team at support@edgenext.com.
Back to documentation home