Dynamic Route for CDN (DCDN) allows you to configure a User-Agent blacklist or whitelist to identify and filter requests. This can restrict access to DCDN resources and improve service security. This topic describes how to configure a User-Agent blacklist or whitelist.
Background information
User-Agent is an HTTP header. It contains the information about the client that sends the request, including the operating system (OS), OS version, browser, and browser version.
- User-Agent blacklist: Requests whose User-Agent header is in the blacklist are rejected. The HTTP 403 status code is returned to the client.
- User-Agent whitelist: Only requests whose User-Agent header is in the whitelist are allowed to access resources on DCDN nodes.
- The blacklist and whitelist are mutually exclusive. You can configure only one of them.
- If a User-Agent field is added to the blacklist, requests that contain the field can still access DCDN nodes. However, DCDN nodes reject these requests and return an HTTP 403 status code. These requests are recorded in the DCDN logs.
Procedure
Configuration examples
- Example 1: Configure a blacklist
Rule:
*IE*|*^$*
Expected result: Requests sent from Internet Explorer (IE) or that do not contain the User-Agent header are rejected.
- Example 2: Configure a whitelist
Rule:
*IE*|*firefox*
Expected result: Only requests sent from IE or Firefox are allowed to access resources on DCDN nodes.