平安云|Ping An Cloud- Building Your Smart Future

Features

What is the difference between the back-to-source host and the source station of CDN? The source station determines the specific IP address that CDN initiates the back-to-source request to, while the back-to-source host determines which site of the IP address the back-to-source request will access to. •   For example, if the source station is www.a.com and the back-to-source host is www.b.com, then CDN initiates the back-to-source request to www.a.com but the IP address that CDN obtains through resolution is www.b.com. •   If the source station is 192.168.1.1 and the back-to-source host is www.b.com, CDN initiates the back-to-source request to 192.168.1.1, which maps the www.b.com on the host. Does any change need to be made to the source station for the acceleration service to apply after it accesses to CDN? Basically, no change is needed. However, to achieve better acceleration result, we recommend you to assign dynamic and static files to different domains and only accelerate the static resources. Does CDN support any port other than 80 for acceleration? CDN acceleration only supports port 80 (HTTP) in original state but will support port 443 (HTTPS) after certificate configuration. Does CDN support POST requests? Yes. CDN supports POST requests. How to identify the CDN node to which the user is accessing? You can acquire basic troubleshooting information such as the IP, latency and lost packet of the CDN node accessed by users by using the commands of ping and nslookup. What are the reasons for a low hit rate? This is generally caused by the following reasons: •   There are cache configuration problems, such as short cache validity period. •   HTTP Header prevents caching. Check the source station's Cache-Control or Expires configurations. •   There are few cacheable content for the source station type. •   Website has less visits and low validity period. Low hit rate for files leads to frequent back-to-source requests. What if my access to CDN is slow? The slow speed of big files may be caused by download speed, while that of small files may be caused by latency. After receiving the feedback, we will first test the Internet speed to determine whether it is slow. (Recommended tool: 17ce) If the situation is true and the server has its own source, we will help the you to check if the machine is overloaded or the bandwidth goes wrong.   Why the size of files with the same name returned by the node is different？ As all file types are cached by default, there may be different versions for a file on the CDN node. To solve this problem: •   Manually refresh files and update cache immediately. •   Use a version number, for example: http://www.xxx.com/xxx.js?version=1. •   Change the file name to avoid using files with the same name.

Did the above content solve your problem? Yes No