Thank you for the links. I am still somewhat disappointed that the http/2 protocol would enforce a certain configuration. I understand the necessity of secure connections, but that's should be left as an option to the developers.
If browsers want to strictly use TLS, that's fine because it's consumer facing, but at least Go should enable http/2 over non-TLS. We are engineers here, we should know the difference. On Wednesday, November 15, 2017 at 12:05:41 PM UTC-8, Howard C. Shaw III wrote: > > See > https://github.com/golang/go/issues/14141 - for discussion of the issue; > and > https://github.com/hkwi/h2c for a way to use the in > stdlib-but-not-linked-together support for h2c (http/2 over non-TLS). > > Howard > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
