Don't specify NextProtos so that we can take advantage of HTTP/2

[aaronjwood]

If we don't specify NextProtos HTTP/2 support will be enable when possible. See golang/go#14374 (comment) and golang/go@b5f0aff

[ghost]

Can one of the admins verify this patch?

[aaronjwood]

Actually, I don't see this TLSListeners method getting called anywhere. Should it be removed?

[aaronjwood]

Going to close this as it looks like TLSListeners is dead code :)

[jonboulle]

This isn't really dead code - it's an exported function that we happen to not use anywhere else internally in this repository ;-). I think this is still appropriate so feel free to re-open

[aaronjwood]

Okay, reopening then :)

[ghost]

Can one of the admins verify this patch?

[jonboulle]

ok to test

On 15 August 2016 at 18:07, Aaron Wood [email protected] wrote:

Okay, reopening then :)

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#191 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACewN5Y5PGr4InmoKnY5fH50bvYcoeekks5qgI6vgaJpZM4Jke2y
.

[jonboulle]

LGTM - any chance you can tweak your commit message though?
activation: remove setting of NextProtos from tls config or similar

[aaronjwood]

Sure, just altered it.