Repository navigation
v0.2.0
Security
- Failure entries and the logger's own error entry log a masked
errorblock (type, message,
file, line, trace, previous) instead of the raw exception, whose message can contain URLs with
API keys (Guzzle appends the request URL, query string included). - Multipart fields with nested names (
payment.card_number,payment[card_number]) are masked
when any name segment is sensitive. - Sensitive XML elements are masked even when they contain child elements.
- Credentials in URLs (
https://user:pass@host) and free-textkey=valuepairs are masked in raw
text. - Masking fails closed: if a pattern cannot run on a body, the body is replaced by a placeholder
instead of being logged unmasked. - Incoming bodies are no longer read in full before the size check:
Content-Lengthis checked
first, otherwise the body is read only up to the limit. Multipart summaries stay within
max_body_bytesas a whole.
Added
log.exception_objectoption to also pass the raw exception object (unmasked) to the logger,
e.g. for error-reporting tools.
Changed
outgoing-failureentries and "http-logger failed to write a log entry" entries no longer
contain theexceptionobject by default; use the newerrorblock, or enable
log.exception_object.
Upgrade note: failure entries no longer include the raw exception object by default. If an error-reporting tool relies on it, set log.exception_object to true.
Full changelog: v0.1.0...v0.2.0