This article will focus on the client-side. Note HTTP protocol is on the basis of client-server model. In this article, we’ll focus on the mechanism of HTTP1.1, but what you learned here can help you understand other new versions of HTTP protocol. Note HTTP protocol itself has evolved a lot from HTTP1.1 to HTTP2 and HTTP3, not to mention HTTPS.
We’ll read a lot of source code and draw diagrams to help your understanding of the source code.
Http client golang how to#
So in this article, we’ll try to understand how to do it by investigating Golang net/http package as an example. Frankly speaking, I can’t work it out by myself in a short period. It turns out to be a very complex and big work in terms of software engineering. Have you ever thought about how we can implement a fully functional HTTP protocol library? Software engineers use HTTP every day and take it for granted. So relatively speaking, HTTP protocol is not as mysterious as other protocols in the lower layers of this stack. I recommend you to read these articles above before this one.Īs you know, HTTP protocol is in the application layer, which is the closest one to the end-user in the protocol stack. Understand how HTTP/1.1 persistent connection works based on Golang: part two - concurrent requests.Understand how HTTP/1.1 persistent connection works based on Golang: part one - sequential requests.How to write a Golang HTTP server with Linux system calls.
In my previous articles, I already wrote several articles about HTTP protocol: I keep planning to write about this topic for a long time. In this article, I’ll write about one topic: how to implement the HTTP protocol.
0 kommentar(er)
