You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Oleg Kalnichevski (JIRA)" <ji...@apache.org> on 2015/07/28 11:25:04 UTC

[jira] [Resolved] (HTTPCLIENT-1670) Httpclient prints different jsessionid for each request

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

Oleg Kalnichevski resolved HTTPCLIENT-1670.
-------------------------------------------
    Resolution: Invalid

No, it does not. Only if one explicitly activates header / wire logging. You are not supposed to run it in production or for anything remotely security sensitive.

Oleg 

> Httpclient  prints different jsessionid for each request 
> ---------------------------------------------------------
>
>                 Key: HTTPCLIENT-1670
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1670
>             Project: HttpComponents HttpClient
>          Issue Type: Bug
>            Reporter: jimmyshen
>
> Httpclient  prints different cookie and  jsessionid for each request.But jseesion is sensitive information for user.so httpclient could provider config to disble print these information.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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