-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Ensure Jetty IO uses SocketAddress instead of InetSocketAddress #6410
Labels
Comments
sbordet
added a commit
that referenced
this issue
Jun 15, 2021
Removed usages of InetSocketAddress in method signatures where possible. Deprecated old methods, and added new methods with SocketAddress. Signed-off-by: Simone Bordet <simone.bordet@gmail.com>
sbordet
added a commit
that referenced
this issue
Jun 15, 2021
Restored fake socket addresses in ByteArrayEndPoint, as too many tests depend on these fake socket addresses. Signed-off-by: Simone Bordet <simone.bordet@gmail.com>
sbordet
added a commit
that referenced
this issue
Jun 15, 2021
Fixed handling of the LOCAL command: everything past it must be ignored as per specification. Signed-off-by: Simone Bordet <simone.bordet@gmail.com>
This is related to Issue #2134 |
sbordet
added a commit
that referenced
this issue
Jun 17, 2021
* Fixes #6410 - Use SocketAddress instead of InetSocketAddress. Removed usages of InetSocketAddress in method signatures where possible. Deprecated old methods, and added new methods with SocketAddress. Signed-off-by: Simone Bordet <simone.bordet@gmail.com>
joakime
changed the title
Use SocketAddress instead of InetSocketAddress
Ensure Jetty IO uses SocketAddress instead of InetSocketAddress
Jun 24, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Target Jetty version(s)
10.0.x
Enhancement Description
In preparation for support of Unix Domain Sockets, introduced in Java 16 and handled in #6043, many Jetty I/O classes should be changed to return/use
SocketAddress
instead ofInetSocketAddress
.As this is a quite large change that is better done separately.
The text was updated successfully, but these errors were encountered: