Forwarding Custom Header Fields

You can use WAF to add additional header information, for example, $request_id, to associate requests on the entire link. You can follow this topic to let WAF insert additional fields into a header and forward requests to origin servers.

Prerequisites

You have selected Cloud - CNAME or Dedicated for Protection when adding the website to WAF.

Constraints

Header field forwarding can be configured only when you select Cloud - CNAME and Dedicated for Protection.
Forwarding custom header fields is supported in some regions. For details, see Functions.
You can configure up to eight key/value pairs.

The value can be set to a custom string or a variable starting with $. Variables starting with $support only the following fields:

$time_local
$request_id
$connection_requests
$tenant_id
$project_id
$remote_addr
$remote_port
$scheme
$request_method
$http_host
$origin_uri
$request_length
$ssl_server_name
$ssl_protocol
$ssl_curves
$ssl_session_reused

Procedure

Log in to the management console.
Click in the upper left corner of the management console and select a region or project.
Click in the upper left corner and choose Web Application Firewall under Security & Compliance.
In the navigation pane on the left, choose Website Settings.
In the Domain Name column, click the website domain name to go to the basic information page.
In the Forward Field column, click . In the displayed Forward Field dialog box, enter a key/value pair. To add more fields, click Add.

Figure 1 Forward Field
After the fields are added, click Confirm.