-
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
:authority header for IPv6 address not having square brackets #5079
Comments
AFAIK, the square brackets for IPv6 addresses are only needed in URIs. I'm not aware of the IETF IPv6 specification to mandate square brackets and I don't think they should be sent in the HTTP/2 I know of HTTP/2 deployments over IPv6 and we have not had reports of problems for lack of square brackets in Do you have any authoritative reference or interoperability issue that confirms the problem? |
What does curl produce when you force http2 and ipv6?
|
Thanks for your response. |
I verified that The client should also take into account |
See #1503. |
…ackets. Fixed Jenkins failures by disabling tests that require IPv6 if it is not available. Signed-off-by: Simone Bordet <simone.bordet@gmail.com>
…ackets. Updates after review. Signed-off-by: Simone Bordet <simone.bordet@gmail.com>
…ackets. Reverted code changes to HttpClient.normalizeHost(). Signed-off-by: Simone Bordet <simone.bordet@gmail.com>
Fixes #5079 - :authority header for IPv6 address not having square br…
Motivation: Commit 8e4d90e merged commit c0e8abf from dependabot[bot] <support@github.com> that resolves a security vulnerability by bumping the Jetty version from 9.4.18.v20190429 to 9.4.34.v20201102. This new version of Jetty resolves issue jetty/jetty.project#5079, with the effect that HttpServletRequest#getRemoteAddr now returns IPv6 addresses in square brackets. Previously, the getRemoteAddr method returned IPv6 addresses without square brackets. The change in format means that calling InetAddresses.forString throws an IllegalArgumentException if dCache's WebDAV or frontend is used with an IPv6 address. Modification: Update Guava usage to a method that expects IPv6 addresses in square brackets. Result: dCache WebDAV and frontend now work with IPv6 interfaces. Target: master Requires-notes: no Requires-book: no
Motivation: Commit 8e4d90e merged commit c0e8abf from dependabot[bot] <support@github.com> that resolves a security vulnerability by bumping the Jetty version from 9.4.18.v20190429 to 9.4.34.v20201102. This new version of Jetty resolves issue jetty/jetty.project#5079, with the effect that HttpServletRequest#getRemoteAddr now returns IPv6 addresses in square brackets. Previously, the getRemoteAddr method returned IPv6 addresses without square brackets. The result of this change in format means that calling Guava's InetAddresses.forString now throws an IllegalArgumentException if dCache's WebDAV or frontend is used with an IPv6 address. Modification: Update Guava usage to a method that expects IPv6 addresses in square brackets. Result: dCache WebDAV and frontend now work with IPv6 interfaces. Target: master Requires-notes: no Requires-book: no Patch: https://rb.dcache.org/r/12671/ Acked-by: Tigran Mkrtchyan Acked-by: Lea Morschel
Jetty version
9.4.30.v20200611
Java version
11
OS type/version
Description
The :authority header Jetty Http Client send out for IPv6 endpoint is
:authority: 2356:0102:3238:3876:1122:2232:4321:80
As per the IPv6 host literal the value should be
[2356:0102:3238:3876:1122:2232:4321]:80
The text was updated successfully, but these errors were encountered: