ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: not.waf@gmail.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:94421] [Ruby master Feature#15215] HTTPS server name indication (SNI): explicit server_name in Net::HTTP
Date: Mon, 19 Aug 2019 01:44:27 +0000 (UTC)	[thread overview]
Message-ID: <redmine.journal-80842.20190819014426.86ef4bd1d5c0d04b@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-15215.20181007092052@ruby-lang.org

Issue #15215 has been updated by waf (felix wong).


aspettl (Aaron Spettl) wrote:
> I still like to have this feature. Any opinion on this? Especially @naruse as a maintainer of lib/net/http(s).rb?
> 
> Thanks!

+1 as well

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

* 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/

  parent reply	other threads:[~2019-08-19  1:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <redmine.issue-15215.20181007092052@ruby-lang.org>
2018-10-07  9:20 ` [ruby-core:89305] [Ruby trunk Feature#15215] HTTPS server name indication (SNI): explicit server_name in Net::HTTP ruby-bugs
2018-10-07  9:45 ` [ruby-core:89307] " ruby-bugs
2018-12-16 18:53 ` [ruby-core:90572] " ruby-bugs
2019-08-19  1:44 ` not.waf [this message]
2019-12-09 11:17 ` [ruby-core:96157] [Ruby master " naruse

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.ruby-lang.org/en/community/mailing-lists/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=redmine.journal-80842.20190819014426.86ef4bd1d5c0d04b@ruby-lang.org \
    --to=ruby-core@ruby-lang.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).