Our Bugsnag is configured for express. When an express request has an error, Bugsnag logs all sorts of useful info about the request, including HTTP headers. The authorization header contains sensitive information and recording them in Bugsnag could violate privacy concerns. Depending on the application, other HTTP headers could contain information that is just as sensitive. Adding adding a configuration filter for authorization should also apply the filter to headers.
Observed behavior
Adding a filter does not apply to headers when used with express.
Expected behavior
Our Bugsnag is configured for express. When an express request has an error, Bugsnag logs all sorts of useful info about the request, including HTTP headers. The authorization header contains sensitive information and recording them in Bugsnag could violate privacy concerns. Depending on the application, other HTTP headers could contain information that is just as sensitive. Adding adding a configuration filter for authorization should also apply the filter to headers.
Observed behavior
Adding a filter does not apply to headers when used with express.