Access URL format
When MD5 value is calculated, if the request path is
http://cloud.tencent.com/test.jpg, then the path used for MD5 calculation will be
TypeA requires the following configuration:
Custom Authentication Key: it contains 6–32 uppercase and lowercase letters and digits. The key should be kept private and known only to the client and server.
Custom Authentication Parameter Name: the
sign in the example can be replaced with a parameter name containing 1–100 uppercase and lowercase letters, digits, and underscores. After CDN receives the request, it will read the value of the specified signature parameter and calculate the MD5 value. If the result matches the
md5hash value passed in, the signature will be successfully verified. If not, a 403 error will be directly returned.
Custom Validity Period: the
timestamp value in the request, plus the configured validity period, is compared with the current time to determine whether the request has expired. If yes, a 403 error will be directly returned.
After configuring the key, parameter name, and validity period, you can specify the authentication object as needed. The following three modes are supported:
Cache hit rate
If you have enabled the TypeA authentication mode for a domain name, the access URL will carry the authentication parameter. When a CDN node caches the resource, it will automatically ignore the authentication parameter and thus not affect the cache hit rate.
The access format of a domain name with TypeA authentication mode enabled is as follows:
If the CDN node is not hit after successful authentication, it will initiate an origin-pull request, which is in the same format as the access request with the
sign parameter retained. The origin server can ignore it or perform authentication again as needed.