[go-nuts] Re: golang and http2

I suggest just using a self-signed cert for your LB<->appserver and disabling cert-checking in your LB. Should be relatively straightforward; you can even have your appserver generate a cert on startup, so there's less messing around with files required. It'll give you http2, and also cheaply p

Re: [go-nuts] Re: golang and http2

One serious potential issue is that the URL scheme is still "http" (or "https") for both. With TLS, the client and server can negotiate an on-the-wire protocol using ALPN. This allows client and server to decide on HTTP 1.1 or http/2 based on what they support. But over plain-text, there is no suc

Re: [go-nuts] Re: golang and http2

It’s really easy to do, see https://github.com/nhooyr/lily/blob/fb72112455ade17f36ed773d87902bb5eefe051e/lily.go#L82-L109 The only disadvantage is that you will not have graceful shutdown. > On Nov

[go-nuts] Re: golang and http2

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 co

[go-nuts] Re: golang and http2

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 "gola