Authentication Method B
Download
Focus Mode
Font Size
Authentication URL format
http://Hostname/timestamp/md5hash/Filenamehttps://Hostname/timestamp/md5hash/Filename
Parameter description
Field | Description |
Hostname | Site Acceleration Domain. |
Path | Resource access path, authentication requires prefixing with /. |
timestamp | UTC+8 Time, format: YYYYMMDDHHMM, e.g., 201807301000. |
md5hash | A fixed length string of 32 bits calculated using the MD5 algorithm: Algorithm: MD5(Key + timestamp + Path). Authentication Logic: If the request has not expired, the node compares this string value with the md5hash value carried in the request URL. If the values are the same, authentication passes, and the request is responded to; if the values are different, authentication fails, returning 403. |
Configuration Samples
Assume the request URL
https://www.example.com/foo.jpg uses Authentication Method B. Since this method prepends the authentication information /{timestamp}/{md5hash} before the actual resource path, the actual URL Path when the request reaches the node is /{timestamp}/{md5hash}/foo.jpg. The rule engine's "URL Path" matching operates on the original request path carrying the authentication prefix, not the actual business path.Therefore, the matching condition must use "Regular Expression Matching" to include the authentication prefix. It cannot be configured based on the actual business path (for example,
URL Path equals /foo.jpg), otherwise the request will fail to match the rule.A configuration example is provided below:
Get authentication parameters:
Path:
/foo.jpg.timestamp: The server-side generated authentication URL time is July 15, 2024, 15:33:50 (UTC+8), expressed in decimal (YYYYMMDDHHmm) format as
202407151533.Key:
DvYmqE81E1F9R791H6lmht.md5hash: MD5(Key + timestamp + Path) = MD5(
DvYmqE81E1F9R791H6lmht202407151533/foo.jpg) = d1f0b51c6894231fc12e054fcc7f0b3e. Authentication URL generated by the client request
https://www.example.com/202407151533/d1f0b51c6894231fc12e054fcc7f0b3e/foo.jpg.Node Authentication
When the Node Server receives a request sent by a client via an encrypted URL, it parses the timestamp parameter from the URL, adds the configured effective duration of "1 second", and compares it with the current time:
1. exceed the "timestamp + effective duration" time, the request is not expired, continue to step 2.
2. The Node Server calculates the md5hash value using the obtained authentication parameters and compares it with the md5hash value carried in the request URL. If the values are the same, authentication passes and the request is responded to; if the values are different, authentication fails, returning 403.
3. After node authentication passes, the system automatically strips the /{timestamp}/{md5hash} prefix and uses the actual business path /foo.jpg to fetch the content from the origin.
Help and Support
Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Help us improve! Rate your documentation experience in 5 mins.
Feedback