Comment 1:

i am not sure we need a new variable.  
it could work for http to look at
TLSClientConfig.InsecureSkipVerify.

Owner changed to @bradfitz.

Status changed to Accepted.

Comment 2:

This issue was closed by revision 2cab897.

Status changed to Fixed.

Comment 3 by jtolds:

Is there any way we can re-open this issue?
I'm working on a distributed system in which none of the hosts have stable
hostnames/IPs/ports. However, we still want to use SSL with both client and server
certificate verification.
Disabling hostname check only when InsecureSkipVerify doesn't do it for us. Is there a
way we can disable the hostname check without setting InsecureSkipVerify?

Comment 4 by jtolds:

(Before you worry whether or not my system is vulnerable to MITM attacks, members of
this distributed system are identified by their public key)

Can we please re-open this issue? There should be an option to verify the certificate chain without verifying the hostname.

https://tools.ietf.org/html/rfc6125#appendix-B.2

...
If the client has external information as to the expected identity of
the server, the hostname check MAY be omitted.  (For instance, a
client may be connecting to a machine whose address and hostname are
dynamic but the client knows the certificate that the server will
present.)
...

I do not wish to cause a duplicate issue with identical title, identical problem, and identical suggested solution "adding an field in either http.Transport or tls.Config like DisableHostnameCheck".