[
https://issues.apache.org/jira/browse/CXF-8896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17740589#comment-17740589
]
Daniel Kulp commented on CXF-8896:
----------------------------------
It IS using HTTP 1.1 by default, but with the option to upgrade to HTTP/2.
The headers above are all valid HTTP 1.1 headers. If the server is rejecting
something in the above, that is a bug in the server, not CXF.
> http client sends some strange HTTP/1.1 and HTTP/2 mix headers
> --------------------------------------------------------------
>
> Key: CXF-8896
> URL: https://issues.apache.org/jira/browse/CXF-8896
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 4.0.2
> Reporter: Jim Ma
> Priority: Major
> Fix For: 4.0.3, 4.1.0
>
>
> From CXF 4.0.1, without the force http version with
>
> {code:java}
> ((BindingProvider)port).getRequestContext().put("org.apache.cxf.transport.http.forceVersion",
> "1.1"), {code}
> The http client sends request with strange headers :
> {code:java}
> POST /jaxws-securityDomain2/authz HTTP/1.1
> Connection: Upgrade, HTTP2-Settings
> Content-Length: 207
> Host: 127.0.0.1:23088
> HTTP2-Settings: AAEAAEAAAAIAAAABAAMAAABkAAQBAAAAAAUAAEAA
> Upgrade: h2c
> Accept: */*
> Content-Type: text/xml; charset=UTF-8
> SOAPAction: ""
> User-Agent: Apache-CXF/4.0.1 {code}
> This works in CXF 4.0.0 and this commit seems introduce issue:
> [https://github.com/apache/cxf/commit/9b36a4bc996615e0ed02795c74167586a2bb11df]
>
> If force the HTTP/1.1 with property :
> org.apache.cxf.transport.http.forceVersion , it works. But this is a backward
> compatible issue and we should still support HTTP/1.1 by default.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
