HTTP Settings
Last update：2026-10-19 14:43:13
Protocol Settings lets you add, replace, or remove HTTP headers and enable HTTP/2.0 for client connections.
Before you begin
- For custom headers, prepare the header name and value before you create the rule.
Configure HTTP header rules
Create an HTTP header rule to add, replace, or remove headers for selected request or response directions.
- In Configuration, open Edit Configuration for the target domain.
- In the navigation pane, choose Protocol Settings > HTTP Header Name.
- Choose Add.
- In the HTTP Header Name dialog, configure the rule.
| Field | Description |
|---|---|
| Rule Scope | Select Specific File Type, Specific Directory, or URL Regular Expression, then enter the matching scope. For Specific Directory, enter one directory path per line. |
| Action | Select Add, Replace, or Remove. See Choose an HTTP header action. |
| HTTP Header Name | Select the HTTP header to add, replace, or remove. |
| Custom HTTP Header Name | Enter a custom header name. For Remove, separate multiple names with semicolons (;). For Add and Replace, enter one name. |
| New Value | For Add or Replace, enter the new header value. |
| Request/Response Direction | Select one or more directions: Request to Origin, Response to Client, Response from Origin, or Request from Client. See Choose the right direction for more details. |
| Priority | Enter the rule priority. |
- Choose Confirm.
Choose an HTTP header action
The action determines how the CDN handles the selected HTTP header.
| Action | Behavior | Use when |
|---|---|---|
| Add | Adds a new HTTP header. Select a header and specify its value in New Value. | CDN should add a header in the selected direction. |
| Replace | Replaces the value of an existing HTTP header. Select a header and enter the replacement in New Value. | CDN should update an existing header value. |
| Remove | Removes one or more HTTP headers. Select a header or enter custom header names. Separate multiple custom names with semicolons (;). |
CDN should remove the selected header from the selected direction. |
Note: Available header choices depend on Action. Select a header offered by the console, or choose Custom and enter a header name. Some header, action, and direction combinations are unsupported; the dialog displays an error if a combination is invalid.
Choose the right direction
The Request/Response Direction field determines where the CDN modifies the header. Select the direction based on the sender and receiver of the request or response.
| Direction | Traffic segment | What it means | Common CDN and streaming use |
|---|---|---|---|
| Request from Client | Player, browser, or application to CDN | A header sent by the playback client before CDN handles the request | Handle request headers such as Accept, Accept-Encoding, Accept-Language, Referer, or User-Agent when the rule is about client request metadata. |
| Request to Origin | CDN to origin | A header sent by CDN when it requests content from the origin | Add or replace origin-facing headers, such as a custom routing header required by the origin. |
| Response from Origin | Origin to CDN | A header returned by the origin before CDN returns the response to the client | Normalize origin response headers before CDN continues response processing. |
| Response to Client | CDN to player, browser, or application | A header visible to the playback client in the final CDN response | Add response headers needed by playback clients, such as CORS headers or content-related headers. |
Configure HTTP/2
Turn on HTTP/2.0 to let CDN use HTTP/2 for client connections.
- In Configuration, open Edit Configuration for the target domain.
- In the navigation pane, choose Protocol Settings > HTTP/2.0.
- Turn on HTTP/2.0.
Note: This setting applies to client connections. Use Origin Protocol Version for origin connections. HTTP/2 origin connections are not supported by all products; contact Technical Support to confirm availability.
Save and submit changes
After confirming a rule or changing a switch, review the configuration. Save Draft saves your work as a draft. To continue through review and submission, choose Next and follow the console prompts. Before testing, check the domain’s configuration status and confirm that the changes have taken effect.