Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

For Https request seeing 2 connections opened by Jetty to serve the request #12879

Open
ravishjasuja opened this issue Mar 6, 2025 · 1 comment
Labels
Bug For general bugs on Jetty side Unsupported Release For releases that are no longer supported

Comments

@ravishjasuja
Copy link

Jetty version(s)
10.0.20

Jetty Environment
Jetty 10

Java version/vendor
Java 11

OS type/version
SLES 15 SP4

Description
When request sent to https port. We are seeing 2 connections opened.
First Connection: For the SSL/TLS handshake.
Second Connection: For the actual HTTP request after the handshake is completed.
Is there a way to optimize it? Is there a way that Jetty can use single connection to serve the https request.
Note: We have separate port which serves http client request and we see only 1 connection opened for that but seeing 2 connection opened for https.

How to reproduce?
We need to fire https request and we can see that 2 connections are opened.

@ravishjasuja ravishjasuja added the Bug For general bugs on Jetty side label Mar 6, 2025
@sbordet
Copy link
Contributor

sbordet commented Mar 6, 2025

Jetty 10 is at end of community support, see:

By the way, Jetty does not do what you describe.

Try with Jetty 12, and if you still see the issue, please report exactly what you mean by "2 connections opened" because I can guarantee you it is not what happens.

@joakime joakime added the Unsupported Release For releases that are no longer supported label Mar 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For general bugs on Jetty side Unsupported Release For releases that are no longer supported
Projects
None yet
Development

No branches or pull requests

3 participants