[
https://issues.apache.org/jira/browse/KNOX-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15733246#comment-15733246
]
Larry McCay commented on KNOX-805:
----------------------------------
[~treydone] - Thank you for the contributions!
I am really excited to see such improvements for the client library.
This one is particularly interesting.
We have come across the desire to provide a custom httpclient in the past as
well.
It was in the context of needing to provide a way to turn configure client side
trust.
I was concerned at that time about leaking the client implementation details
through the programming model.
I think that I am still concerned about that and would like to pursue the
ability to configure the items described here in a way that doesn't leak that
implementation detail before we go down that road.
What I'd like to avoid is having to continue to support httpclient due to
direct dependencies in client code - in case a new client comes along that
would be better for some reason.
Thoughts?
> Allow defining a custom HttpClient when creating a new session
> --------------------------------------------------------------
>
> Key: KNOX-805
> URL: https://issues.apache.org/jira/browse/KNOX-805
> Project: Apache Knox
> Issue Type: Bug
> Components: ClientDSL
> Reporter: Vincent Devillers
> Assignee: Vincent Devillers
>
> When creating a new session, I think it should be possible to specify a
> custom CloseableHttpClient in parameter of the static method
> Hadoop.login(url, user,password). This will allow to prepare a well defined
> CloaseableHttpClient if you want to add headers, limit the length of the
> message send, define specific strategy on dns resolution or hostname
> verification, size the connection pool…
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
