In Protocol Settings, you can add, replace, or remove HTTP headers in selected request or response directions, and you can enable HTTP/2 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.

1. In Configuration, open Edit Configuration for the target domain.
2. In the navigation pane, choose Protocol Settings > HTTP Headers.
3. Choose Add.
4. In the HTTP Headers dialog, configure the rule.

Field	Description
Apply to	Select Specific File Type, Specific Directory, or URL Pattern (Regex). Use this field to scope the rule to the playback paths, file extensions, or URL patterns that require the header change. For Specific Directory, enter directory paths, one per line.
Action	Select Add, Replace, or Remove. Choose the action based on whether the header is missing, has the wrong value, or should not be passed in the selected direction.
HTTP Headers	Select the HTTP header to add, replace, or remove.
Custom HTTP Header	Enter a custom HTTP header. For Remove, you can enter multiple headers separated by semicolons (;). For Add and Replace, enter only one header.
Old Value	Appears for Replace. Enter the existing header value to be replaced.
New Value	Enter the new header value.
Apply Rule to	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.

5. Choose Confirm.

Choose an HTTP Header Action

The action determines how Atomile 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.	Atomile should add a header in the selected direction.
Replace	Replaces the value of an existing HTTP header. Select a header, then specify Old Value and New Value.	Atomile should replace a known header value with another value.
Remove	Removes one or more HTTP headers. Select one or more headers to remove, separated by semicolons (;).	Atomile should remove the selected header from the selected direction.

Restriction: Some headers support only specific actions and directions. If the selected header, action, and direction combination is not supported, the dialog displays an error.

Choose the Right Direction

The Apply Rule to field controls the traffic direction where Atomile processes the header. Select the direction based on who sends the message and who receives the modified message.

Direction	Traffic Segment	What It Means	Common CDN and Streaming Use
Request from Client	Player, browser, or application to Atomile	A header sent by the playback client before Atomile handles the request	Handle request headers such as Accept, Accept-Encoding, Accept-Language, Referer, or User-Agent when the rule applies to client request metadata.
Request to Origin	Atomile to origin	A header sent by Atomile when it requests content from the origin	Add or replace origin-facing headers, such as a custom host or routing header required by the origin.
Response from Origin	Origin to Atomile	A header returned by the origin before Atomile returns the response to the client	Normalize origin response headers before Atomile continues response processing.
Response to Client	Atomile to player, browser, or application	A header visible to the playback client in the final Atomile response	Add response headers needed by playback clients, such as CORS headers or content-related headers.

Configure HTTP/2

Enable HTTP/2 to let Atomile use HTTP/2 for client connections.

1. In Configuration, open Edit Configuration for the target domain.
2. In the navigation pane, choose Protocol Settings > HTTP/2.
3. Enable HTTP/2.

The HTTP/2 switch shows the enabled state.

Note: HTTP/2 enables HTTP/2 for client connections. To configure connections to your origin, use Origin Protocol Version. Not all products support HTTP/2 for origin connections. Contact Technical Support for more details.

Reference

Supported Header Actions

Category	Header	Supported Actions	Supported Directions
Accept-related	Access-Control-Allow-Origin	Add, Replace, Remove	Response headers
Accept-related	Access-Control-Allow-Methods	Add, Replace, Remove	Response headers
Accept-related	Accept	Add, Replace, Remove	Request headers
Accept-related	Accept-Encoding	Add, Replace, Remove	Request headers
Accept-related	Accept-Charset	Add, Replace, Remove	Request headers
Accept-related	Accept-Language	Add, Replace, Remove	Request headers
Accept-related	Accept-Ranges	Add, Replace, Remove	Request headers
Content-related	Content-Base	Replace	Response headers
Content-related	Content-Disposition	Replace	Response headers
Content-related	Content-Encoding	Replace	Response headers
Content-related	Content-Language	Replace	Response headers
Content-related	Content-Location	Replace	Response headers
Content-related	Content-MD5	Replace	Response headers
Content-related	Content-Range	Replace	Response headers
Content-related	Content-Type	Replace	Response headers
Cache-related	Vary	Add, Replace, Remove	Response headers
State-related	Cookie	Add, Replace, Remove	Request headers
State-related	Set-Cookie	Add, Replace, Remove	Response headers
Other	Referer	Replace	Request headers
Other	Server	Replace	Response headers
Other	User-Agent	Replace	Request headers
Other	Custom header	Add, Replace, Remove	Request or response headers