研究了一下 golang 的http2 用法
這里先普及幾個概念
- h2薄霜,基于TLS之上構(gòu)建的HTTP/2,作為ALPN的標(biāo)識符纸兔,兩個字節(jié)表示惰瓜,0x68, 0x32,即https
- h2c汉矿,直接在TCP之上構(gòu)建的HTTP/2崎坊,缺乏安全保證,即http
在HTTP/2 RFC文檔出現(xiàn)之前洲拇,以上版本字段需要添加上草案版本號奈揍,類似于h2-11,h2c-17
首先寫了一個服務(wù)器的代碼
import (
"fmt"
"html"
"net/http"
"golang.org/x/net/http2"
)
func main() {
var server http.Server
http2.VerboseLogs = true
server.Addr = ":8080"
http2.ConfigureServer(&server, &http2.Server{})
http.HandleFunc("/", func(w http.ResponseWriter, r *http.Request) {
fmt.Fprintf(w, "URL: %q\n", html.EscapeString(r.URL.Path))
ShowRequestInfoHandler(w, r)
})
server.ListenAndServe() //不啟用 https 則默認(rèn)只支持http1.x
//log.Fatal(server.ListenAndServeTLS("localhost.cert", "localhost.key"))
}
func ShowRequestInfoHandler(w http.ResponseWriter, r *http.Request) {
// fmt.Fprintf(w, "======")
// return
w.Header().Set("Content-Type", "text/plain")
fmt.Fprintf(w, "Method: %s\n", r.Method)
fmt.Fprintf(w, "Protocol: %s\n", r.Proto)
fmt.Fprintf(w, "Host: %s\n", r.Host)
fmt.Fprintf(w, "RemoteAddr: %s\n", r.RemoteAddr)
fmt.Fprintf(w, "RequestURI: %q\n", r.RequestURI)
fmt.Fprintf(w, "URL: %#v\n", r.URL)
fmt.Fprintf(w, "Body.ContentLength: %d (-1 means unknown)\n", r.ContentLength)
fmt.Fprintf(w, "Close: %v (relevant for HTTP/1 only)\n", r.Close)
fmt.Fprintf(w, "TLS: %#v\n", r.TLS)
fmt.Fprintf(w, "\nHeaders:\n")
r.Header.Write(w)
}
由于不想 使用https 就使用了 server.ListenAndServe(),沒想到這里有個坑赋续,等下介紹
既然服務(wù)端使用了http 非 tls 那么 客戶端就使用 非 tls 了男翰,看代碼
package main
import (
"crypto/tls"
"fmt"
"io/ioutil"
"log"
"net"
"net/http"
"golang.org/x/net/http2"
)
func main() {
url := "http://localhost:8080/"
client(url)
}
func client(url string) {
log.SetFlags(log.Llongfile)
tr := &http2.Transport{ //可惜服務(wù)端 退化成了 http1.x
AllowHTTP: true, //充許非加密的鏈接
// TLSClientConfig: &tls.Config{
// InsecureSkipVerify: true,
// },
DialTLS: func(netw, addr string, cfg *tls.Config) (net.Conn, error) {
return net.Dial(netw, addr)
},
}
httpClient := http.Client{Transport: tr}
resp, err := httpClient.Get(url)
if err != nil {
log.Fatal(err)
}
defer resp.Body.Close()
if resp.StatusCode != http.StatusOK {
fmt.Println("resp StatusCode:", resp.StatusCode)
return
}
body, err := ioutil.ReadAll(resp.Body)
if err != nil {
log.Fatal(err)
}
fmt.Println("resp.Body:\n", string(body))
}
由于http2 client 沒有暴露 h2c 模式的,所以就 搞了個
AllowHTTP: true, //充許非加密的鏈接
DialTLS: func(netw, addr string, cfg *tls.Config) (net.Conn, error) {
return net.Dial(netw, addr)
},
本意是想這樣實現(xiàn)客戶端h2c
搞完了就運行服務(wù)器纽乱,執(zhí)行客戶端蛾绎,結(jié)果打印
Get http://localhost:8080/: unexpected EOF
看的云里霧里,再抓包一看
服務(wù)器向客戶端發(fā)了一個http1.1 的包迫淹,并且還close 了client 鏈接秘通,為什么會這樣呢
server.ListenAndServe() //不啟用 https 則默認(rèn)只支持http1.x
既然服務(wù)器只支持http1 了那么客戶端 發(fā)http2的請求,服務(wù)器當(dāng)然要close 鏈接了敛熬。
那么有沒有辦法解決呢肺稀,即服務(wù)器和客戶端都使用 h2c ,客戶端的比較好辦 AllowHTTP: true 充許非加密的鏈接 并且
DialTLS: func(netw, addr string, cfg *tls.Config) (net.Conn, error) {
return net.Dial(netw, addr)
},
服務(wù)端考慮使用更低一層的庫http2庫實現(xiàn),主要是使用ServCon直接替換掉net/http/中的serv函數(shù)应民,例如
import (
"fmt"
"golang.org/x/net/http2"
"net/http"
"net"
"time"
)
//net/http包默認(rèn)可以采用http2進行服務(wù)话原,在沒有進行https的服務(wù)上開啟H2夕吻,
//需要修改ListenAndServer的默認(rèn)h2服務(wù)
type serverHandler struct {
}
func (sh *serverHandler) ServeHTTP(w http.ResponseWriter, req *http.Request) {
fmt.Println(req)
w.Header().Set("server", "h2test")
w.Write([]byte("this is a http2 test sever"))
}
func main() {
server := &http.Server{
Addr: ":8080",
Handler: &serverHandler{},
ReadTimeout: 5 * time.Second,
WriteTimeout: 5 * time.Second,
}
//http2.Server.ServeConn()
s2 := &http2.Server{
IdleTimeout: 1 * time.Minute,
}
http2.ConfigureServer(server, s2)
l, _ := net.Listen("tcp", ":8080")
defer l.Close()
fmt.Println("Start server...")
for {
rwc, err := l.Accept()
if err != nil {
fmt.Println("accept err:", err)
continue
}
go s2.ServeConn(rwc, &http2.ServeConnOpts{BaseConfig: server})
}
//http.ListenAndServe(":8888",&serverHandler{})
}