[
https://issues.apache.org/jira/browse/HTTPCLIENT-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17743184#comment-17743184
]
Dominik Derwiński commented on HTTPCLIENT-2283:
-----------------------------------------------
No need to get touchy. I didn't expect it to happen, merely suggested it might
be a good idea, as sometimes when you're deeply into some code you can't see
issues casual user will. And let me quote you the following page (relevant
fragments): https://hc.apache.org/get-involved.html
There are plenty of ways to help outside writing code. [...], feature
suggestions, reporting bugs, documentation and usability feedback all matter
immensely.
What did I do wrong here? I did just that.
> 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
