Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

proposal: net: Add support for HTTP/3(QUIC). #36961

Closed
CodingByteFly opened this issue Feb 1, 2020 · 2 comments
Closed

proposal: net: Add support for HTTP/3(QUIC). #36961

CodingByteFly opened this issue Feb 1, 2020 · 2 comments

Comments

@CodingByteFly
Copy link

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

$ go version 
go version go1.13.5 windows/amd64

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

go env Output
$ go env
set GO111MODULE=on
set GOARCH=amd64
set GOBIN=
set GOCACHE=F:\GoLang\GOCACHE
set GOENV=D:\LOVEL\Documents\GoLang\GOENV\env
set GOEXE=.exe
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=F:\GoLang\GOPATH
set GOPRIVATE=
set GOPROXY=https://goproxy.cn,direct
set GOROOT=D:\Program-Files\GoLang
set GOSUMDB=sum.golang.org
set GOTMPDIR=F:\GoLang\GOTMPDIR
set GOTOOLDIR=D:\Program-Files\GoLang\pkg\tool\windows_amd64
set GCCGO=gccgo
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=NUL
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0 -fdebug-prefix-map=F:\GoLang\GOTMPDIR\go-build781419050=/tmp/go-build -gno-record-gcc-switches

What did you do?

Web develop

What did you expect to see?

As we known, HTTP/3(QUIC) is better than HTTP/2.
But when I

import "net"
I found that it can't support HTTP/3(QUIC). I think it is bad for the development of HTTP/3(QUIC). Go originated in Google, and HTTP/3(QUIC) was also developed by Google. I think if the stardard library of Go can support HTTP/3(QUIC), it will benefit for the development of Go and HTTP/3(QUIC).

What did you see instead?

As we known, HTTP/3(QUIC) is better than HTTP/2.
But when I

import "net"
I found that it can't support HTTP/3(QUIC).

@CodingByteFly CodingByteFly changed the title I hope standard library can add support for HTTP/3. net: I hope standard library can add support for HTTP/3. Feb 1, 2020
@CodingByteFly CodingByteFly changed the title net: I hope standard library can add support for HTTP/3. net: I hope standard library can add support for HTTP/3(QUIC). Feb 1, 2020
@CodingByteFly CodingByteFly changed the title net: I hope standard library can add support for HTTP/3(QUIC). proposal: net: I hope standard library can add support for HTTP/3(QUIC). Feb 1, 2020
@gopherbot gopherbot added this to the Proposal milestone Feb 1, 2020
@CodingByteFly CodingByteFly changed the title proposal: net: I hope standard library can add support for HTTP/3(QUIC). proposal: net: Add support for HTTP/3(QUIC). Feb 1, 2020
@mvdan
Copy link
Member

mvdan commented Feb 1, 2020

HTTP/3 is only a draft as of December 2019, right? Following what was done for HTTP/2, it seems to me like the work should happen in the x/net repo first, and become part of the standard library once the final version is out.

@mvdan
Copy link
Member

mvdan commented Feb 1, 2020

Also, this is a duplicate of #32204.

@mvdan mvdan closed this as completed Feb 1, 2020
@golang golang locked and limited conversation to collaborators Feb 3, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants