[
https://issues.apache.org/jira/browse/HTTPCLIENT-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17743110#comment-17743110
]
Dominik Derwiński commented on HTTPCLIENT-2283:
-----------------------------------------------
Thanks, missed it.
I got to say the hardest part of using Apache Client is configuring it. Too
many mixed styles (constructor arguments, setters, builders), and dozens of
classes to handle all abstractions... What people usually want to configure are
timeouts, socket keep alive/no delay and sometimes ssl context / ciphers. You
could make it easier, you know :)
> Missing option to configure charset for classic CloseableHttpClient
> -------------------------------------------------------------------
>
> Key: HTTPCLIENT-2283
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2283
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: HttpClient (classic)
> Affects Versions: 5.2.1
> Reporter: Dominik Derwiński
> Priority: Major
>
> In http client 4 I could use ConnectionConfig.custom().setCharset &
> BasicHttpClientConnectionManager.setConnectionConfig (or
> PoolingHttpClientConnectionManager.setDefaultConnectionConfig) &
> HttpClients.custom().setConnectionManager.
> In http client 5 for async client I can use
> CharCodingConfig.custom().setCharset &
> HttpAsyncClients.custom().setCharCodingConfig.
> I don't see an option to set this for
> org.apache.hc.client5.http.impl.classic.CloseableHttpClient in
> HttpClients.custom() or elsewhere.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org
