---
title: Configure HTTP response headers
description: Configure standard name-value pairs for HTTP response headers. You designate if the configuration applies to all pages, or to specific types \(Service Portal, UI Page, or UX application record\).The HTTP response header table \(sys\_response\_header\) in the List view contains two additional columns - Add by and Order.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/servicenow-platform/configure-http-response-header.html
release: australia
topic_type: task
last_updated: "2026-03-12"
reading_time_minutes: 3
breadcrumb: [HTTP Response Headers, Extend ServiceNow AI Platform capabilities]
---
# Configure HTTP response headers
Configure standard name-value pairs for HTTP response headers. You designate if the configuration applies to all pages, or to specific types \(Service Portal, UI Page, or UX application record\).
## Before you begin
Role required: An elevated access security\_admin role is required to configure an **All Pages** type header. An admin role is required to configure a **Specific Type** header.
## Procedure
1. In the Navigator pane, type `sys_response_header.list`.
2. Click **New**.
3. Fill in the fields on the form.
|
Field
|
Description
|
|---|
|
Active
|
Check box that designates that this HTTP response header configuration is active.
|
|
Application
|
Application scope for this record.
|
|
Applies to
|
Type of record the HTTP response header configuration applies to.- **Specific Type**
HTTP response header configuration is for the specific type and record you select in the **Type** and **Record** fields.
- **All Pages**
HTTP response header configuration is for all pages and record types.
**Note:** Only users with an elevated access privilege security\_admin role can configure HTTP response headers for the All Pages type header.
|
|
Type
|
Type of record the HTTP response header configuration applies to. - **Service Portal \[sp\_portal\]**
Records related to the Service Portal.
- **UI Page \[sys\_ui\_page\]**
Standard UI pages in the ServiceNow AI Platform.
- **UX Application \[sys\_ux\_page\_registry\]**
Standard UX applications in the ServiceNow AI Platform.
|
|
Record
|
Specific record the HTTP response header configuration applies to. To select a record:1. Click the Search \(\[Omitted image "List\_SearchIcon.png"\] Alt text: Search icon\) icon to access the Select the document form.
2. In the **Table name** field, the default is the type you selected in the **Type** field. Do not change it.
3. In the **Document** field, select the record from the table.
For example, if you selected **Service Portal \[sp\_portal\]**, you select a specific Service Portal-related record in that table.
4. Click **OK**.
You can only access this field if you selected **Specific Type** in the **Applies to** field.
|
|
Name
|
Name you want to assign to the name-value pair for the HTTP response header.
|
|
Value
|
Value you want to assign to the name-value pair for the HTTP response header.
|
|
Description
|
Detailed description for the HTTP response header.
|
4. Click **Submit**.
## HTTP header configuration for advanced users
The HTTP response header table \(sys\_response\_header\) in the List view contains two additional columns - **Add by** and **Order**.
|
Column
|
Description
|
|---|
|
Order
|
Adds a default integer order value to a header configuration regardless of the type of header \(**All Pages** or a **Specific page**\). - When a specific page request takes place, both of the header types are interleaved based on the **Order**.
- The net headers, regardless of the type, are sorted first, based on the **Order** and added to the response based on the ordered header list.
|
|
Add By
|
Contains the following values:- **Append**
\(Default value\) This option is relevant when multiple headers with the same name are configured. In this case, they are both added to the HTTP response header.
- **Overwrite**
This option is relevant when the same header \(a header with the same name\) is attempting to add twice in the ordered header list \(see **Order** description\). The header with the higher order and with an **Overwrite** selection in **Add By** overwrites the same header trying to be set with a lower order.
|
You may have situations where a couple of similar **All Pages** type header configurations could overwrite a **Specific Type** type header configuration. An example of a **Specific Type** configuration would be one for a specific UI page. You can remedy this situation by adjusting the **Add by** and **Order** columns, as in the following examples.
### Append example
The ServiceNow AI Platform is trying to set headers in the following order, and **Append** is the default value for each in the **Add By** column. \[Omitted image "headers-all-append-list-view.jpg"\] Alt text: Append example - sys\_response\_header.list
In this example, the second \(Header 2\) and third \(Header 3\) response header configurations have the same name \(Content-Security-Policy\). In this case, Header 3 is appended to Header 2. If a request is made for a specific page you configured with a Header 3 response, the net HTTP response headers are both Header 2 and Header 3.
\[Omitted image "headers-all-append-page-response.png"\] Alt text: Append example - resulting HTTP response header
### Overwrite
The ServiceNow AI Platform is trying to set headers in the following order, and you've selected **Overwrite** in the **Add By** column for the third header. \[Omitted image "headers-one-overwrite-list-view.jpg"\] Alt text: Overwrite example - sys\_response\_header.list
In this example, the second \(Header 2\) and third \(Header 3\) response header configurations have the same name \(Content-Security-Policy\). In this case, Header 3 overwrites Header 2. If a request is made for a specific page you configured with a Header 3 response, the net HTTP response header is only Header 3.
\[Omitted image "headers-one-overwrite-page-response.png"\] Alt text: Overwrite example - resulting HTTP response header