Improve TLS mismatch error messages/experience

[BrennanConroy]

• Grpc hits this a lot
• HTTP -> HTTPS
• HTTPS -> HTTP
• H2C -> HTTP(S)

[ghost]

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[Tratcher]

Nginx has a special status code for that:
497 HTTP Request Sent to HTTPS Port
http://nginx.org/en/docs/http/ngx_http_ssl_module.html

[Tratcher]

Note H2C -> HTTPS endpoint would trigger the same checks and message as HTTP -> HTTPS because of the connection preface unless we special cased the HTTP/2 prefface PRI * HTTP/2.0\r\n\r\nSM\r\n\r\n.

[Tratcher]

@JamesNK this looks like a duplicate of another issue you were working on?

[JamesNK]

I improved the mismatch between HTTP/1.1 and HTTP/2. I haven't done anything for TLS.

[Tratcher]

What was the issue number?

[JamesNK]

#14884

Yes, this can be closed as a dupe.