HTTP response headers
HTTP response headers let clients and servers pass additional information with an HTTP request or response. In Collibra, you can configure the HTTP response headers to improve security against a wide range of threats, such as Cross-Site-Scripting (XSS), UI redressing (clickjacking), MIME type sniffing and other types of attacks.
Configuration of HTTP response headers and scopes
HTTP response headers are configured in scopes, which consist of a URL pattern and one or more HTTP response headers. On each request, Collibra checks the URL and uses the HTTP response headers of all matching URL patterns.
The tables below shows the out-of-the-box HTTP response headers and their URL patterns.
Collibra Platform
| URL pattern | HTTP response header | |
|---|---|---|
|
Name |
Value |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/rest/**
|
|
default-src 'none';
|
|
|
|
|
|
|
|
SAMEORIGIN
|
|
|
default-src 'none';
|
|
|
|
|
|
|
|
|
|
/graphql/batch
|
|
|
|
|
|
|
| URL pattern | HTTP response header | |
|---|---|---|
|
Name |
Value |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/rest/**
|
|
default-src 'none';
|
|
|
|
|
|
|
|
SAMEORIGIN
|
|
|
default-src 'none';
|
|
|
|
|
|
|
|
|
|
/graphql/batch
|
|
|
|
|
|
|
| URL pattern | HTTP response header | |
|---|---|---|
|
Name |
Value |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/rest/**
|
|
default-src 'none';
|
|
|
|
|
|
|
|
SAMEORIGIN
|
|
|
default-src 'none';
|
|
|
|
|
|
|
|
|
|
| URL pattern | HTTP response header | |
|---|---|---|
|
Name |
Value |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/rest/**
|
|
default-src 'none';
|
|
|
|
|
|
|
|
SAMEORIGIN
|
|
|
default-src 'none';
|
|
|
|
|
|
|
|
|
|
Collibra Console
| URL pattern | HTTP response header | |
|---|---|---|
|
Name |
Value |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/rest/**
|
|
default-src 'none';
|
|
|
|
|
|
|
|
|
|
|
|
|
| URL pattern | HTTP response header | |
|---|---|---|
|
Name |
Value |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/rest/**
|
|
default-src 'none';
|
|
|
|
|
|
|
|
|
|
|
|
|
Whitelists
Whitelists contain the list of trusted web domains to allow safe client-side integrations. Similar to explicit web domains, you can use references to whitelists in HTTP response headers to ignore the HTTP response headers for trusted web domains.
If you have the required permissions, you can edit the whitelists of the HTTP response headers.
Recommended use
You can include web domains and references to whitelists in the HTTP response headers. Collibra will then ignore the HTTP response headers for all web domains mentioned explicitly and in the whitelists.
However, you need the SUPER role in Collibra Console to edit the HTTP response headers, which allows you to edit the entire HTTP response header, and much more. You only need the ADMIN role to edit the whitelists. This means that you cannot edit the HTTP response header themselves. Therefore, working with whitelists is considered to be safer.
|
Whitelist name |
Placeholder to use in the HTTP response header |
|---|---|
| connect-src |
{connectSrcWl} |
| font-src |
{fontSrcWl} |
| frame-src |
{frameSrcWl} |
| img-src |
{imgSrcWl} |
| script-src |
{scriptSrcWl} |
| style-src |
{styleSrcWl} |
| frame-ancestors |
{frameAncestorsWl} |
| Tableau frame-ancestors |
{tableauFrameAncestorsWl} |
Web domain format and wildcards
Each whitelist can contain any number of web domains. You can also use the asterisk (*) as a wildcard to match a broader range of web domains.
|
Format |
Description |
|---|---|
|
<protocol><subdomain>.<second-level domain>.<top-level domain> |
Match a specific protocol and a specific web domain. Example
Web domain: Matches: Calls to |
|
<protocol>*.<second-level domain>.<top-level domain> |
Match a specific protocol and all subdomains of a web domain. Example
Web domain: Matches: Calls to any subdomain of |
| *.<second-level domain>.<top-level domain> |
Match all subdomains of a web domain, with the current protocol. Example
Web domain: Matches: Calls to any subdomain of |
|
<subdomain>.<second-level domain>.<top-level domain>:* |
Match all ports of a specific web domain. Example
Web domain: Matches: Calls to any port on |
|
<subdomain>.<second-level domain>.<top-level domain>:<port> |
Match a specific port of a specific web domain. Example
Web domain: Matches: Calls to port |
Further reading
For more information about HTTP response headers, see the following external sources: