-
Notifications
You must be signed in to change notification settings - Fork 4.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
backport 1.13: http: fixing a bug with IPv6 hosts #14464
backport 1.13: http: fixing a bug with IPv6 hosts #14464
Conversation
Signed-off-by: alyssawilk <alyssar@chromium.org>
Signed-off-by: Shikugawa <rei@tetrate.io>
It would be good to understand the test failures seen on both the 1.13 and 1.14 backports. The changes in this PR don't seem to be related to those failures. |
I think that the test failures are related to expired certificates. That was the reason for failures on 1.15 branch. I am investigating it. |
interesting. What was the fix on 1.15? |
The fix was to re-run a script which generates new set of certs valid until 2022: test/config/integration/certs/certs.sh. I think the same problem may exists in test/extensions/transport_socket/tls. |
I assume we should backport the certs generated to 1.14 and 1.13 also. |
…port-1.13/13798 Signed-off-by: Shikugawa <Shikugawa@gmail.com>
Do you know what's up with CI here? I kicked off a second run and it failed too. |
It fails in |
@Shikugawa I figured out why the test fails.
|
/retest |
Retrying Azure Pipelines: |
2469c3b
to
b32c71b
Compare
@cpakulski I found that the creation of the new cert chain is not quite. So it will be caused some strange |
Signed-off-by: Shikugawa <Shikugawa@gmail.com>
b32c71b
to
2612bd9
Compare
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.
I think I said on the last PR it'd be good to split out TLS changes. Can we do that here and elsewhere? Sorry/thanks!
Created #14594 to bring TLS changes and make fake_upstream to use localhost. @Shikugawa Once #14594 is merged to 1.13 you can bring it here. |
Signed-off-by: Shikugawa <Shikugawa@gmail.com>
/retest |
Retrying Azure Pipelines: |
Signed-off-by: Shikugawa <Shikugawa@gmail.com>
Fixing a bug where HTTP parser offsets for IPv6 hosts did not include [] and Envoy assumed it did.
This results in mis-parsing addresses for IPv6 CONNECT requests and IPv6 hosts in fully URLs over HTTP/1.1
Risk Level: low
Testing: new unit, integration tests
Docs Changes: n/a
Release Notes: inline