Conversation
Support IP addresses in host headers. This completes the MVP of dynamic forward proxy. Fixes #1606 Signed-off-by: Matt Klein <mklein@lyft.com>
|
@lizan @PiotrSikora PTAL I'm sure I got something wrong here either on the TLS or spec side. cc @alyssawilk |
alyssawilk
left a comment
There was a problem hiding this comment.
Looks good! (modulo defering TLS magic to TLS folks =P)
Signed-off-by: Matt Klein <mklein@lyft.com>
Signed-off-by: Matt Klein <mklein@lyft.com>
Signed-off-by: Matt Klein <mklein@lyft.com>
Signed-off-by: Matt Klein <mklein@lyft.com>
|
@alyssawilk @lizan @PiotrSikora updated per comments. |
Signed-off-by: Matt Klein <mklein@lyft.com>
PiotrSikora
left a comment
There was a problem hiding this comment.
Hmm, I was sure that I saw it before, but I cannot find it now... Could you add a test that verifies that using IP address in "verify_subject_alt_name" works against peer with "upstreamlocalhostcert.pem"?
Will do. |
Signed-off-by: Matt Klein <mklein@lyft.com>
Signed-off-by: Matt Klein <mklein@lyft.com>
|
@PiotrSikora updated with the test you asked for. |
Signed-off-by: Matt Klein <mklein@lyft.com>
|
/retest |
|
🔨 rebuilding |
PiotrSikora
left a comment
There was a problem hiding this comment.
LGTM, sans the explicit IPv4 and IPv6 tests.
|
@PiotrSikora @lizan I pushed an update per your comments, but I'm seeing what I think is a persistent flake in coverage which I don't think is due to my changes: I will take a look tonight or tomorrow but LMK if you have any thoughts. I'm assuming it's somehow due to the sharding we now have. |
|
I don't see anything in the code that should break that test. |
Support IP addresses in host headers.
This completes the MVP of dynamic forward proxy.
Fixes #1606
Risk Level: Low
Testing: Unit and integration tests
Docs Changes: N/A
Release Notes: N/A