Create HTTP response headers for Engagement Messenger
Configure a name-value pair for HTTP response headers for the Engagement Messenger module. The ability to configure and pass response headers enables special handling of the page content by a client, which is most typically a browser.
Before you begin
- Configure Engagement Messenger.
- Create an identity provider (IdP) for Engagement Messenger.
- Configure a CORS rule for Engagement Messenger.
- Role required: admin
About this task
Use the Engagement Messenger API and your website URL to create a CORS rule.
Procedure
In the navigation pane, enter
sys_response_header.list.Select New.
On the form, fill in the fields.
| Field | Description |
|---|---|
| Active | Option for indicating that this HTTP response header configuration is active. |
| Application | Application scope for this record. |
| Applies to | Type of record that the HTTP response header configuration applies to. Select Specific Type to indicate that this HTTP response header configuration is for the specific type and record that you select in the Type and Record fields. |
| Type | Type of record that the HTTP response header configuration applies to. Select Service Portal to indicate that the records are related to the Service Portal. |
| Record | Engagement Messenger module record that the HTTP response header configuration applies to. Select a record:
|
| Name | Name for the name-value pair for the HTTP response header. Set this field value to Content-Security-Policy. |
| Value | Value for the name-value pair for the HTTP response header. Set this field value to frame-ancestors 'self' <enter your website URL>. For example, frame-ancestors 'self' https://www.example.com. |
| Description | Detailed description for the HTTP response header. |
What to do next
Activate an Engagement Messenger module
.
Related topics