Adding or modifying headers on HTTP requests and responses

  Last updated 2023-04-25

HTTP header fields are components of the header section of request and response messages in the Hypertext Transfer Protocol (HTTP). They define the operating parameters of an HTTP transaction. When you create and configure headers, you can determine how you want your content served to your users. The following steps show you how to add and edit headers.

Create new headers

  1. Log in to the Fastly web interface.
  2. From the Home page, select the appropriate service. You can use the search box to search by ID, name, or domain.
  3. Click Edit configuration and then select the option to clone the active version.
  4. Click Content.

  5. Click Create header.

    Create a header

  6. Fill out the Create a header fields as follows:

    • In the Name field, enter the name of your header rule (for example, My header).
    • From the Type menu, select Request, and from the Action menu, select Set.
    • In the Destination field, enter the name of the header affected by the selected action.
    • In the Source field, enter where the content for the header comes from.
    • From the Ignore if set menu, select No if you want the header in the Destination field modified or select Yes if you don't want it modified.
    • In the Priority field, enter the order the header rules execute.

    The Field description table below provides additional details about each of these controls.

  7. Click Create.

  8. Click Activate to deploy your configuration changes.

Edit headers

  1. Log in to the Fastly web interface.
  2. From the Home page, select the appropriate service. You can use the search box to search by ID, name, or domain.
  3. Click Edit configuration and then select the option to clone the active version.
  4. Click Content.

  5. Click the name of the header you want to edit.

    the Edit this header window

  6. Fill out the Edit this header fields as follows:

    • In the Name field, enter the name of your header rule (for example, My header).
    • From the Type menu, select Request, and from the Action menu, select Set.
    • In the Destination field, enter the name of the header affected by the selected action.
    • In the Source field, enter where the content for the header comes from.
    • From the Ignore if set menu, select No if you want the header in the Destination field modified or select Yes if you don't want it modified.
    • In the Priority field, enter the order the header rules execute.

  7. Click Update.

  8. Click Activate to deploy your configuration changes.

Field description table

This table describes what each field in the Header window means:

FieldDescription
NameThe Name field specifies a memorable word or phrase that allows you to recognize and remember a particular Header rule.
TypeThe Type menu can be set to Request, Response, or Cache. Selecting Request modifies the request coming from the user, and this will carry through to the request that gets sent to your origin server. Selecting Response affects the HTTP response that is sent back to the user. Selecting Cache affects the HTTP response that your origin server returns before it gets stored on Fastly servers, meaning whatever changes you make there will be remembered on a cache hit.
ActionThe Action menu can be set to Set, Append, Delete, Regex, and Regex All. Selecting Set (the default) will write a value into the header (potentially overwriting it, if it already exists). Selecting Append will add a value onto the end of a header or set it if it doesn't exist. Selecting Delete will remove a header. When selected, it hides the Source field in the Header window. Selecting Regex allows you to perform a find and replace on specific text and is based on a regular expression you type in. When selected, the Regex and Substitution controls appear in the Header window. Selecting Regex All allows you to perform the same function as Regex but it performs a find and replace multiple times. When selected, the Regex and Substitution controls appear in the Header window.
DestinationThe Destination field determines the name of the header that is going to be affected by our Action. Because header rules can be used to affect more than just HTTP headers, your input to this field should be formatted like this: http.Header-Name.
SourceThe Source field is available on Set, Append, Regex, and Regex All actions. This field becomes hidden in the Header window when you select Delete from the Action menu. It determines where the new content for the header comes from. There are a plethora of options for Source. The simplest is a static string such as "My Static String" (including the quotes). Other options include client.ip, req.http.Another-Header, and client.geo.city. See the list of Common Sources below for more common sources of new content.
RegexThe Regex field only appears in the Header window when you select Regex or Regex All from the Action menu. It allows you to perform a find and replace on specific text and is based on a regular expression that you type in.
SubstitutionThe Substitution field only appears in the Header window when you select the Regex and Regex All from the Action menu. It replaces the text that was removed by the regex expression with the text you typed in the Substitution field.
Ignore if setBy default this is set to No, which means that if the header you are modifying already exists, it will be modified.
PriorityThe Priority field determines the order in which the header rules execute (e.g., a priority of 1 means the header rule executes first). This can be important if you set headers and then set other headers based on the earlier ones.

Common sources of new content

NameValid TypesDescription
req.http.Fastly-Client-IPRequest, Cache, ResponseThe true IP address of the client.
client.ip and client.identityRequest, Cache, ResponseThe client IP address. These variables are available, but may not always display the source IP address. For instance, they may show the edge node IP when shielding is enabled. For the true client IP address, use req.http.Fastly-Client-IP.

IMPORTANT: In some cases, client IP data may be considered sensitive. Make sure you protect the sensitive IP data you stream or store.
server.identityRequest, Cache, ResponseA unique identifier for the Fastly server processing the request.
server.regionRequest, Cache, ResponseThe region in which the Fastly server resides.
server.datacenterRequest, Cache, ResponseThe data center in which the Fastly server resides.
req.urlRequest, Cache, ResponseThe URL of the HTTP Request from the client.
req.http.*Request, Cache, ResponseThe headers from the HTTP Request, access as: req.http.HeaderName
beresp.statusCacheThe status returned from the origin server.
beresp.http.*CacheThe headers from the origin's HTTP Response, access: beresp.http.HeaderName
resp.statusResponseThe status that is going to be returned to the client.
resp.http.*ResponseThe headers in the HTTP Response to be returned to the client, access: resp.http.HeaderName
client.geo.*Request, Cache, ResponseGeolocation values for the client's IP.
Was this guide helpful?

Do not use this form to send sensitive information. If you need assistance, contact support. This form is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Fastly
© Fastly 2023