-
Notifications
You must be signed in to change notification settings - Fork 1.4k
fix: 🐛 request.url getter fails when using IPv6 and HTTP2 [#4560] #4559
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
Open
gsoldevila
wants to merge
1
commit into
hapijs:master
Choose a base branch
from
gsoldevila:fix/4556-protect-invalid-ipv6-in-request-url
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
fix: 🐛 request.url getter fails when using IPv6 and HTTP2 [#4560] #4559
gsoldevila
wants to merge
1
commit into
hapijs:master
from
gsoldevila:fix/4556-protect-invalid-ipv6-in-request-url
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
3eb41e7 to
4f47a71
Compare
gsoldevila
commented
Nov 7, 2025
|
|
||
| const req = request.raw.req; | ||
| const host = req.headers.host ? req.headers.host.trim() : ''; | ||
| const host = (req.headers.host || req.headers[':authority'] || '').trim(); |
Author
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps we could test if the req is an IPv6 request somehow, and choose Host or :authority accordingly. WDYT?
This was referenced Nov 7, 2025
gsoldevila
added a commit
to elastic/kibana
that referenced
this pull request
Nov 11, 2025
…#242241) ## Summary Workarounds #236380 The official way to address this is with the following issue + PR on hapijs/hapi side: * hapijs/hapi#4560 * hapijs/hapi#4559 Until then, we can inject the Host information that Hapi relies on when it builds the `url` string.
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Nov 11, 2025
…elastic#242241) ## Summary Workarounds elastic#236380 The official way to address this is with the following issue + PR on hapijs/hapi side: * hapijs/hapi#4560 * hapijs/hapi#4559 Until then, we can inject the Host information that Hapi relies on when it builds the `url` string. (cherry picked from commit 0d41ec2)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Nov 11, 2025
…elastic#242241) ## Summary Workarounds elastic#236380 The official way to address this is with the following issue + PR on hapijs/hapi side: * hapijs/hapi#4560 * hapijs/hapi#4559 Until then, we can inject the Host information that Hapi relies on when it builds the `url` string. (cherry picked from commit 0d41ec2)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Nov 11, 2025
…elastic#242241) ## Summary Workarounds elastic#236380 The official way to address this is with the following issue + PR on hapijs/hapi side: * hapijs/hapi#4560 * hapijs/hapi#4559 Until then, we can inject the Host information that Hapi relies on when it builds the `url` string. (cherry picked from commit 0d41ec2)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Nov 11, 2025
…elastic#242241) ## Summary Workarounds elastic#236380 The official way to address this is with the following issue + PR on hapijs/hapi side: * hapijs/hapi#4560 * hapijs/hapi#4559 Until then, we can inject the Host information that Hapi relies on when it builds the `url` string. (cherry picked from commit 0d41ec2)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #4560
Problem
In HTTP2 the
Host:header is no longer present. According to the spec:Host:header.Host:header is missing, so the request.url getter) uses thehost:portfrom the _core.info.::1), the getter ends up building an invalid URL, as the host name is not surrounded by square brackets. An IPv6 address like2001:db8::1:8080would be ambiguous, as8080could be interpreted as the last segment of the IP address rather than the port.Solution
The PR updates the request logic in 2 places:
:authorityifHostheader is NOT present.::1) in square brackets[::1].