Giacomo Carnevale created CXF-8906:
--------------------------------------
Summary: Upgrade, HTTP2-Settings - Apache-CXF/3.6.1
Key: CXF-8906
URL: https://issues.apache.org/jira/browse/CXF-8906
Project: CXF
Issue Type: Bug
Components: JAX-WS Runtime, Soap Binding, Transports
Affects Versions: 3.6.1
Environment: Apache CXF 3.6.1
Apache Camel 3.21.0
Java 11
Reporter: Giacomo Carnevale
Fix For: 3.5.6
Hi
I am using Apache Camel CXF component to integrate soap services.
Recently, I updated Apache Camel Version (3.20.x -> 3.21.0) and so is changed
Apache CXF version (3.5.6 -> 3.6.1).
*CXF 3.6.1*
When I invoke SOAP service, by tcpdump I can see that CXF sets http headers
'{*}Connection: Upgrade, HTTP2-Settings{*}', '{*}HTTP2-Settings:
AAEAAEAAAAIAAAABAAMAAABkAAQBAAAAAAUAAEAA{*}' and '{*}Upgrade: h2c{*}' but the
connection is HTTP/1.1:
{code:java}
.o.91v..POST /my-soap-service HTTP/1.1
Connection: Upgrade, HTTP2-Settings
Host: myhost:8080
HTTP2-Settings: AAEAAEAAAAIAAAABAAMAAABkAAQBAAAAAAUAAEAA
Transfer-encoding: chunked
Upgrade: h2c
Accept: */*
Authorization: Basic ******
Content-Type: text/xml; charset=UTF-8
SOAPAction: ""
User-Agent: Apache-CXF/3.6.1{code}
The server responds with {*}HTTP/1.1 101 Switching Protocols{*}.
*CXF 3.5.6*
I excluded CXF dependencies from Apache Camel and I downgraded it to 3.5.6
version and there wasn't this problem
{code:java}
.\....X
POST /my-soap-service HTTP/1.1
Content-Type: text/xml; charset=UTF-8
Accept: */*
Authorization: Basic ******
SOAPAction: ""
User-Agent: Apache-CXF/3.5.6
Cache-Control: no-cache
Pragma: no-cache
Host: my-host:8080
Connection: keep-alive
Transfer-Encoding: chunked {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
