[
https://issues.apache.org/jira/browse/HTTPCLIENT-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17554260#comment-17554260
]
Michael Osipov commented on HTTPCLIENT-2224:
HTTPCLIENT-2159 will require some time to
[
https://issues.apache.org/jira/browse/HTTPCLIENT-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17554190#comment-17554190
]
Oleg Kalnichevski commented on HTTPCLIENT-2224:
---
[~javedbhayla] I am not sure
[
https://issues.apache.org/jira/browse/HTTPCLIENT-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17554170#comment-17554170
]
Javed Bhayla commented on HTTPCLIENT-2224:
--
Ok, thank you, so will the issue I described be
[
https://issues.apache.org/jira/browse/HTTPCLIENT-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski resolved HTTPCLIENT-2224.
---
Resolution: Invalid
`CharCodingConfig` allies to HTTP/1.1 connection
[
https://issues.apache.org/jira/browse/HTTPCLIENT-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17554132#comment-17554132
]
Michael Osipov commented on HTTPCLIENT-2224:
There is a similar bugs for content types
[
https://issues.apache.org/jira/browse/HTTPCLIENT-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17554132#comment-17554132
]
Michael Osipov edited comment on HTTPCLIENT-2224 at 6/14/22 2:29 PM:
Javed Bhayla created HTTPCLIENT-2224:
Summary: US_ASCII used instead of charset configuration in
CharCodingConfig
Key: HTTPCLIENT-2224
URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2224
[
https://issues.apache.org/jira/browse/HTTPCORE-715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17554025#comment-17554025
]
Graham Leggett commented on HTTPCORE-715:
-
Looks like the authoritative source is: