http.Server always responses with http/1.1!

[mziraki]

What version of Go are you using (go version)?

1.7.4

What operating system and processor architecture are you using (go env)?

os: windows
arch: amd64

What did you do?

package main

import (
	"log"
	"net/http"
)

func main() {
	http.HandleFunc("/", func(w http.ResponseWriter, req *http.Request) {
		w.Write([]byte("This is an example server.\n"))
	})
	log.Fatalln(http.ListenAndServeTLS(":443", "certificate.crt", "private.key", nil))
}

What did you expect to see?

http/2 response

What did you see instead?

http/1.1 response, what did I do wrong in sample code above?

[bradfitz]

This bug report is inconsistent. There are two totally different code fragments.

Then I also don't understand the last bit about http2.golang.org. It works fine for me. What is "disable incorrectly" about it?

I think this is best for a question to the mailing list. See https://golang.org/wiki/Questions.

[mziraki]

@bradfitz I cleaned up my question, can you check it again, please. this issue affected my project performance because of http/1.1 responses
Thanks

[bradfitz]

Your updated bug report is no longer inconsistent, but it's also not very useful as a bug report, since it lacks so much information. The code you now cite (for the record: currently just Hello World http.ListenAndServeTLS) should work, and has tests making sure it works. So it's the problem with your client or how you're determining what the protocol version is.

I think this is best discussed on the mailing list (see https://golang.org/wiki/Questions). There is nothing actionable here as a bug report.

[mziraki]

@bradfitz I asked my question here because I thought this problem occurred because google chrome dropped NPN support and golang http package uses NPN to switch to http/2
can this be my client problem that you referred to?

[bradfitz]

That is not the issue. Go has done ALPN for over two years (4 releases) now, since d0e255f