Issue #15215 has been updated by naruse (Yui NARUSE).


Duplicated with #5180.
Since there're 3 layers:
* host address for TCP/IP
* TLS server name
* HTTP Host header

In this use case, I think you wan to set different value for IP layer.
If you forget to change HTTP Host header, it will cause unexpected result if the server uses VirtualHost.

I understand this ticket and related GitHub PRs as +1 for #5180, and I reopen it and commit.

----------------------------------------
Feature #15215: HTTPS server name indication (SNI): explicit server_name in Net::HTTP
https://bugs.ruby-lang.org/issues/15215#change-83033

* Author: aspettl (Aaron Spettl)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
----------------------------------------
**Current behavior and problem:**
At the moment, the host name or IP address given in the URL is used to provide the server name for SNI in HTTPS connections. While this behavior is sufficient in most cases, establishing a connection to a fixed IP using a certain server name is not possible.

**Proposed solution:**
Decouple the server name used for SNI from the address used for connecting. Add a new ssl_server_name attribute in Net::HTTP that defaults to the address (so the default behavior stays exactly the same).

**Notes**
* There are scenarios where a client would like to select a specific host when e.g. DNS round robin is configured. Examples: fallback strategies, monitoring of individual hosts.
* This has nothing to do with the HTTP "Host" header, which one needs to set additionally.

For my "proposed solution", a patch is attached (or see https://github.com/ruby/ruby/pull/1977).
Please let me know about any ideas for improvement or other approaches, thanks!

---Files--------------------------------
ssl_server_name.patch (2.17 KB)


-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>