---
title: Header links
summary: null
url: https://www.fastly.com/documentation/guides/next-gen-waf/header-links
---
Header links facilitate cross-referencing Next-Gen WAF data with your own internal systems via a hyperlink. We currently support linking either request or response headers to any system (e.g., Kibana).
For example, an `X-Request-ID` request header or `X-User-ID` response header can be linked directly to one of your internal systems.
## Creating header links
### Next Gen Waf Control Panel
1. Log in to the [Next-Gen WAF control panel](https://dashboard.signalsciences.net).
2. From the **Sites** menu, select a site if you have more than one site.
3. From the **Manage** menu, select **Header Links**.
4. Click **Add header link**.
5. In the **Header name** field, enter the name of the header (e.g., `X-Request-ID`).
6. From the **Header type** menu, select whether the header is a **Request Header** or a **Response Header**.
7. In the **Link template** field, enter the link to your internal system with the value replaced with the string `{{value}}`.
For example, assume `https://internal-system.example.com/search?X-Forwarded-For&203.0.113.1/results` is the search URL for an internal system which displays all results that contained both the `X-Forwarded-For` header and the IP address `203.0.113.1`.
To use this URL as the header link template URL for the `X-Forwarded-For` header, you would replace `203.0.113.1` with `{{value}}` in the URL. This makes the link generic and not specific to that single IP address. The header link template URL would then be `https://internal-system.example.com/search?X-Forwarded-For&{{value}}/results`.
8. In the **Display name** field, enter the name of the internal system. This name is used in the header links in the Next-Gen WAF control panel. For example, entering `Kibana` will title the link `View in Kibana`.
### Fastly Control Panel
1. Log in to the [Fastly control panel](https://manage.fastly.com).
2. Go to **Security** > **Next-Gen WAF** > [**Workspaces**](https://manage.fastly.com/security/ngwaf/workspaces).
3. Click the gear 
next to the workspace that you want to modify.
4. Click **Header Links** and then **Add Header Link**.
5. In the **Header name** field, enter the name of the header (e.g., `X-Request-ID`).
6. From the **Header type** menu, select whether the header is a **Request Header** or a **Response Header**.
7. In the **Link template** field, enter the link to your internal system with the value replaced with the string `{{value}}`.
For example, assume `https://internal-system.example.com/search?X-Forwarded-For&203.0.113.1/results` is the search URL for an internal system which displays all results that contained both the `X-Forwarded-For` header and the IP address `203.0.113.1`.
To use this URL as the header link template URL for the `X-Forwarded-For` header, you would replace `203.0.113.1` with `{{value}}` in the URL. This makes the link generic and not specific to that single IP address. The header link template URL would then be `https://internal-system.example.com/search?X-Forwarded-For&{{value}}/results`.
8. In the **Display name** field, enter the name of the internal system. This name is used in the header links in the Fastly control panel. For example, entering `Kibana` will title the link `View in Kibana`.
## Using header links
To view the link in action, click **View request detail** in the Next-Gen WAF control panel or the document icon 
in the Fastly control panel.
Underneath either **Request headers** or **Response headers**, next to the header you specified, you will see a header link (e.g., **View in Kibana**). Clicking this link will take you to that internal system with results for that specific header and value.
## Related content
- [Client IP addresses](https://www.fastly.com/documentation/guides/next-gen-waf/client-ip-addresses)
- [Using an API with the Next-Gen WAF](https://www.fastly.com/documentation/guides/next-gen-waf/developer/using-an-api-with-the-next-gen-waf)