{"version":"2.1.228","anchor":"api-key-header-is-now-redacted-in-logs","canonical_anchor":"api-key-header-is-now-redacted-in-logs","heading":"api-key header is now redacted in logs","tier":"notice","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/api-key-header-is-now-redacted-in-logs","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### `api-key` header is now redacted in logs\n\nAn API key sent in the api-key header is now masked in logs.\n\n**What**\n\nHeader dumps mask `api-key` alongside `authorization`, `x-api-key`, `cookie` and `set-cookie`, so an API key passed in that header no longer appears in logs.\n\n**Details**\n\n- The socket messaging mismatch warning also passes the message type and session id through a sanitizer before logging.\n\n**Evidence**\n\n`t.toLowerCase() === \"api-key\"`\n\n- Area: Internals\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}