-
Notifications
You must be signed in to change notification settings - Fork 1.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
Set ServerName (SNI). #377
Comments
I would consider this as a bug actually, just based on how I expect an https stack to work. But I think we should add a separate switch to manually override the SNI again. So domain fronting will still be possible. |
Yes I rather agree.
Have updated my fork:
|
Great, thank you. Let's hope it gets upstreamed soon! |
merged, i just need to release, though i want to release with go 1.19 but need to fix tests #390 |
I think there's a pretty strong argument for setting the ServerName (SNI) to the value of --hostname.
It's pretty much standard to set the ServerName in the TLS ClientHello when a hostname is requested. Regardless, being able to set the SNI is something that's been requested a few times.
The changes are straightforward, won't require a new command line switch and don't appear to be beyond the scope of things (especially seeing as we have --hostname already)
I've submitted a pull request here: #376
The text was updated successfully, but these errors were encountered: