Menu

Request header collection

AppSignal collects headers for HTTP requests by default for supported frameworks. This data may help track down errors or performance issues that were caused by requests header data a client is sending.

To comply with GDPR rules, collecting no user identifiable data, AppSignal collects a very limited amount of headers by default.

To even further limit the request headers or collect more than the default list of headers, configure AppSignal which headers to collect.

Do not send Personal Identifiable Information (PII) to AppSignal. You must ensure that PII (such as personal names, email addresses, passwords, etc.) is filtered before data is sent to AppSignal. If you must identify a person, consider using a user ID, hash or pseudonymized identifier instead.

Configure headers

An app's session data can be filtered by configuring keys in an allowlist. This allowlist system will filter out all the session data keys not in this list.

All headers that are filtered out by these systems are not collected, neither the header name or value.

Read our guide about setting up request header collection and filtering for your app.

Filter all request headers

To filter all request headers without individual header filtering, configure the allowlist to an empty list in the integration configuration. Without any header names in the list, it will not collect any request headers.

A non-exhaustive list of request header names that may be used by an application. Do not include these headers, and those like it, in the integrations "request headers" allowlist unless absolutely necessary.

  • Any personal identifiable headers:
    • IP Addresses
      • Forwarded
    • Browser type and versions headers
      • User-Agent
      • Referrer
        • Referer
    • Passwords and tokens
      • Authorization
      • Proxy-Authorization
      • Any custom API token headers.

See also