[
https://issues.apache.org/jira/browse/HTTPCLIENT-2342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883348#comment-17883348
]
Oleg Kalnichevski edited comment on HTTPCLIENT-2342 at 9/20/24 4:48 PM:
------------------------------------------------------------------------
[~ctabin] Please report this issue to whoever built the `SAINETV4` server and
ask them to fix it. In the meantime one can disable automatic protocol upgrade
by using custom `RequestConfig` with `protocolUpgradeEnabled` set to false.
Oleg
was (Author: olegk):
[~ctabin] Please report this issue to whoever build the `SAINETV4` server and
ask them to fix it. In the meantime one can disable automatic protocol upgrade
by using custom `RequestConfig` with `protocolUpgradeEnabled` set6 to false.
Oleg
> Regression: Content-Type header not returned anymore
> ----------------------------------------------------
>
> Key: HTTPCLIENT-2342
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2342
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpClient (classic)
> Affects Versions: 5.4-beta1
> Reporter: Cedric Tabin
> Priority: Major
>
> Hello,
> We just upgraded today to httpclient5 version 5.4. It seems that the header
> `Content-Type` is not returned anymore by the API, even when listing all the
> headers.
> {code:java}
> client.execute(httpRequest, r -> {
> //does not print Content-Type header
> for(Header h : r.getHeaders()) {
> System.out.println("## "+h.getName()+": "+h.getValue());
> }
> System.out.flush();
> return null;
> });
> {code}
> We can ensure that the `Content-Type` header is well set by the server by
> browsing to the same URL and inspecting the network.
> Our code didn't change and with the version 5.3.1, the Content-Type is
> correctly received.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
