-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Caddyfile support for TLS handshake matchers #6461
Conversation
Thanks! I'm curious where this will be used. The Caddyfile tends to abstract away TLS configuration matching. |
It is a part of mholt/caddy-l4#217 code that I propose to move here for consistency. It will be used in layer4 module configuration. |
- caddytls.MatchLocalIP - caddytls.MatchRemoteIP - caddytls.MatchServerName
ffd177b
to
eb6a04d
Compare
Rebased it on master. Don't know why linter is failing. |
The linter config we have is picky about grouping and ordering of imports. I'll circle back in a bit with a command to fix it |
- fix imports order Co-authored-by: Francis Lavoie <[email protected]>
0c48ee3
to
f0817fa
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.
Thanks for the great contribution, @vnxme 😃
This PR is related to mholt/caddy-l4#217. It implements caddyfile support for TLS handshake matchers:
local_ip
by caddytls.MatchLocalIPremote_ip
by caddytls.MatchRemoteIPsni
by caddytls.MatchServerNameP.S. I noticed, we have NotRanges in caddytls.MatchRemoteIP, but don't have them in caddytls.MatchLocalIP. Shall we fix this inconsistency as well?