This series is a hands-on journey into HTTP/3. We’ll dissect the protocol, explore its practical applications with Go, and navigate the common quirks you might encounter. Perfect for developers looking to leverage modern web protocols for faster, more reliable applications.
Learn how to use HTTP/3 DATAGRAMs in Go for unreliable data transmission.
Previous parts: Writing HTTP3 Server HTTP3 Client Server Stream Today we will create our own HTTP/3 client stream to send some sweet-sweet data to the server. Streaming data from the client can be used for sending large or real-time data uploads, such as file uploads, telemetry, or live feeds. With HTTP/3 and Go, you can efficiently stream request bodies without buffering the entire payload in memory. Streaming Client Request This is similar to streaming a request body in regular HTTP. We鈥檒l use an io.Pipe to write data from the client as it becomes available, while the server reads the stream as it arrives. ...
Previous parts: Writing HTTP3 Server HTTP3 Client Server-side streaming allows you to send data to the client as it becomes available, rather than waiting for the entire response to be ready. This is particularly useful for applications that require reliable real-time updates, such as chat applications, live feeds, or large file transfers. Streaming Server Response This part is similar to the regular HTTP response streaming via http.ResponseWriter. We will stream data from the server as soon as it becomes available, without buffering. For this, we will use the http.Flusher interface, which allows us to flush the response buffer to the client immediately. For reference on how to implement a basic HTTP/3 server, check out Writing HTTP3 Server. ...
Previous parts: Writing HTTP3 Server Today, we will create an HTTP/3 client to interact with our HTTP/3 Server. First of all, you鈥檒l need a running HTTP/3 server. Run it in a separate terminal: go run server.go Client skipping TLS verification Let鈥檚 write a simple HTTP/3 client for our server. It鈥檚 pretty straightforward: we need to create a new HTTP/3 transport and pass it to an HTTP client from net/http. Because HTTP/3 is built on top of QUIC, it requires us to use TLS. Since we are using a self-generated certificate in the server, the client can鈥檛 verify the certificate. One of the options is to skip TLS verification on the client: ...
Today, we will go through the process of setting up a simple HTTP/3 server and verifying its functionality. We will be using quic-go for for this purpose. Generating Certificate Since HTTP/3 requires all traffic to be encrypted, we鈥檒l need a certificate. For our test, we can generate a self-signed TLS certificate for localhost. Go has a build-in tool, which you can run like this: go run $(go env GOROOT)/src/crypto/tls/generate_cert.go --host localhost $(go env GOROOT) will evaluate to the GOROOT path for whatever version of Go you are using. ...