You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to have a logbook property where I can both disable servlet filters but also LogbookExchangeFilterFunction. Seems like logbook.filter.enabled property is only intended for servlet filter support as far as I can see in LogbookAutoConfiguration. Can this property also be used for http client logging?
Detailed Description
I am using [email protected] together with [email protected]. And when I set logbook.filter.enabled=false, only the servlet logging gets disabled, but the WebClient logging still occurs. I am not sure if this is as by design or is a bug.
Context
This is important because users of this library can use a single property to enable/disable request/response logging. And since LogbookExchangeFilterFunction requires a logbook bean which is autoconfigured based on properties, why not leveraging the property to disable/enable the logging.
Your Environment
Version used: 3.9.0
The text was updated successfully, but these errors were encountered:
I would like to have a logbook property where I can both disable servlet filters but also
LogbookExchangeFilterFunction
. Seems likelogbook.filter.enabled
property is only intended for servlet filter support as far as I can see inLogbookAutoConfiguration
. Can this property also be used for http client logging?Detailed Description
I am using
[email protected]
together with[email protected]
. And when I setlogbook.filter.enabled=false
, only the servlet logging gets disabled, but theWebClient
logging still occurs. I am not sure if this is as by design or is a bug.Context
This is important because users of this library can use a single property to enable/disable request/response logging. And since
LogbookExchangeFilterFunction
requires alogbook
bean which is autoconfigured based on properties, why not leveraging the property to disable/enable the logging.Your Environment
The text was updated successfully, but these errors were encountered: