Skip to content

Conversation

@JackOfMostTrades
Copy link

@JackOfMostTrades JackOfMostTrades commented Jun 15, 2018

This is the same option and the same semantics that node.js provides via the "servername" attribute, or that golang provides via the "ServerName" option.

@k0kubun k0kubun changed the base branch from trunk to master August 15, 2019 17:34
@DamirSvrtan
Copy link

Are there any blockers for this to get merged in?

@JackOfMostTrades JackOfMostTrades force-pushed the http-allow-servername branch 3 times, most recently from bef0aba to 722910b Compare August 19, 2019 19:32
@JackOfMostTrades
Copy link
Author

After a little bit of fighting with git, I've rebased this PR over the latest master revision.

@matzbot matzbot closed this in 54072e3 Dec 9, 2019
hsbt pushed a commit to ruby/net-http that referenced this pull request Feb 21, 2020
to replace the address for TCP/IP connection [Feature #5180]

There're 3 layers of hostname:
* host address for TCP/IP
* TLS server name
* HTTP Host header value
To test DNS round robin or check server certificate from server local,
people sometimes want to connect server with given IP address but keep
TLS server name and HTTP Host header value.

closes [Feature #15215]
closes ruby/ruby#1893
closes ruby/ruby#1977
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants