v3.0.3

New Features:

• RequestLoggingFilter adds correlation id as response header X-CorrelationID

Bugfixes:

• request logs contain correlation id when it was generated by RequestLoggingFilter

Improvements:

• travis CI build succeeds using Java 11

v3.0.2

New Feature:

• DropWizard based Custom Metrics client
• Configuration of MDC fields as Custom Fields

Updates:

• jackson-databind to version 2.9.9.1

v3.0.1

Dependency version Update:

• Jackson to 2.9.9
• Java-JWT to 2.8.1

Refactoring of http header code

v3.0.0

This major release introduces two new features:

• Tenantid as an additional HTTP header field
• Custom application metrics

V2.2.3

Changelog

Bump dependencies to fix potential security vulnerabilities.

V2.2.2

Changelog

• update Java-Jwt library
• fix Bug in WrappedOutputStream that prevented flushes of the response output stream of the ServletFilter

V2.2.0

Changelog:

• support async dispatch for RequestLoggingFilter (fixes #24)
• adds MDC context map as request attribute in RequestLoggingFilter

V2.1.5

Changelog:

• Minor improvements and bug fixes for the dynamic log level feature.

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