[ 
https://issues.apache.org/jira/browse/HTTPCLIENT-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oleg Kalnichevski resolved HTTPCLIENT-1908.
-------------------------------------------
    Resolution: Won't Fix

Martin
This feature is too specific to your particular application. The main problem 
is not logging on a per host basis as such rather configuration that it would 
require.   

One can easily plug in a custom {{ManagedHttpClientConnection}} implementation 
with whatever custom behavior that might be required by a specific application 
context. Please see 
[LoggingManagedHttpClientConnection|https://github.com/apache/httpcomponents-client/blob/4.5.x/httpclient/src/main/java/org/apache/http/impl/conn/LoggingManagedHttpClientConnection.java]
 which could serve as a good starting point.

Oleg


> Enable Wire Logging on a per host basis instead of globally
> -----------------------------------------------------------
>
>                 Key: HTTPCLIENT-1908
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1908
>             Project: HttpComponents HttpClient
>          Issue Type: Improvement
>          Components: HttpClient (classic)
>    Affects Versions: 4.5.5
>         Environment: Any; but we are currently running on Windows VMs
>            Reporter: Martin Bosak
>            Priority: Minor
>
> We use http components to communicate with various back end systems (some 
> dealing with very sensitive data (e.g. passwords).
> Often we need to turn on wire logging for other, less sensitive data; but 
> doing so also turns on logging for the sensitive services as well.
> It would be great if we could configure logging for just certain host only. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org

Reply via email to