[jira] Commented: (HTTPCLIENT-1050) Kerberos - HttpClient doesn't cache the generated ticket.

["Oleg Kalnichevski (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HTTPCLIENT-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992154#comment-12992154 ] 

Oleg Kalnichevski commented on HTTPCLIENT-1050:
-----------------------------------------------

Gaurav, 
Could you please provide some details as to what bits you think HttpClient should be caching and for how long?

Header wire + context log of the HTTP session that exhibits the problem would be also quite welcome:

http://hc.apache.org/httpcomponents-client-ga/logging.html

Oleg

 

> Kerberos - HttpClient doesn't cache the generated ticket.
> ---------------------------------------------------------
>
>                 Key: HTTPCLIENT-1050
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1050
>             Project: HttpComponents HttpClient
>          Issue Type: Bug
>          Components: HttpAuth
>    Affects Versions: 4.1 Final
>            Reporter: Gaurav Singhal
>             Fix For: 4.2 Final
>
>
> ClassName: NegotiateScheme
> HttpClient doesn't cache the generated token so that It can be reused in the subsequent Http request.
> This is resulting generating the same token again and again whenever you communicate to kerberized service.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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