[
https://issues.apache.org/jira/browse/CXF-9127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andriy Redko resolved CXF-9127.
-------------------------------
Resolution: Not A Problem
The WebClient in now using JDK's HttpClient under the hood which is itself
using {color:#000000}{color:#000000}sun.nio.ch.SocketChannelImpl. {color}{color}
{color:#000000}{color:#000000}If you would like to continue using old
URLConnection, please please
https://cxf.apache.org/docs/client-http-transport-including-ssl-support.html#ClientHTTPTransport(includingSSLsupport)-DefaultClientTransport{color}{color}
> SSL connection not closed since CXF 4.0.1
> -----------------------------------------
>
> Key: CXF-9127
> URL: https://issues.apache.org/jira/browse/CXF-9127
> Project: CXF
> Issue Type: Bug
> Reporter: Xilai Dai
> Priority: Major
> Attachments: test-ssl.zip
>
>
> When CXF 3.5.x or 4.0.0, the SSL connection will be closed as expected after
> GET operation via WebClient.
> {code}
> javax.net.ssl|DEBUG|91|Keep-Alive-Timer|2025-04-14 08:47:34.005
> CST|SSLSocketImpl.java:1785|close the SSL connection (passive)
> {code}
> With CXF 4.0.1 or above version, there is no "close the SSL connection"
> anymore when print SSL debug information.
> The main difference is the Response Entity object:
> - sun.net.www.protocol.http.HttpURLConnection$HttpInputStream (CXF 3.5.5)
> -
> org.apache.cxf.transport.http.HttpClientHTTPConduit$HttpClientFilteredInputStream
> (CXF 4.1.0)
> Attached a test project for easily reproduce the issue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
