Releases: SAP/cf-java-logging-support
Releases · SAP/cf-java-logging-support
V2.1.4
Changelog:
A minor bug that could lead to performance issues has been fixed.
V2.1.3
Changelog:
- Optional fields that can contain sensitive user data have been extended to
remote_ip, remote_host, remote_port, x_forwarded_for, remote_user, referer. - By default, these fields will not be logged by the Servlet Filter and by the Jersey Filters anymore. Logging of these fields can be activated via the following environment variables:
Environment Variable | Optional Fields |
---|---|
LOG_SENSITIVE_CONNECTION_DATA: true |
activates the fields remote_ip, remote_host, remote_port, x_forwarded_for |
LOG_REMOTE_USER: true |
activates the field remote_user |
LOG_REFERER: true |
activates the field referer |
See also https://github.com/SAP/cf-java-logging-support/wiki/Overview#logging-sensitive-user-data
V2.1.2
Changelog:
- Logging Remote IPs is now optional. It can be activated by adding the environment variable: "LOG_REMOTE_IP: true"
- Java JWT update to version 3.3.0
- Bugfix: When using logback, a valid Json-Object is created now, even if the log message is null
- Minor fixes
V2.1.1
Changelog:
- Longer stack traces are now supported
- The dynamic log level feature allows to change the log level threshold for one single request
- Java version changed from 1.6 to 1.8
- some minor fixes
V2.0.11
Version 2.0.10
Updated log4j2 dependency to support latest version 2.7.
Due to incompatible API changes in log4j2, will not work with older versions anymore!