/explore
|
You are here 
|
aarol.dev | ||
| | | | |
hjr265.me
|
|
| | | | | I know many will start with something like Gin whenever they are working on a JSON/HTTP-based backend in Go. I, not entirely sure if the minority, try to stick to Go's built-in net/http package and, at most, use Gorilla Mux in most of my Go projects. And so serving something simple like JSON is no different from the package's point of view as any other content type: whatever it is, write it out to the w, the http. | |
| | | | |
mmhaskell.com
|
|
| | | | | [AI summary] A tutorial series begins by defining custom Haskell data types to parse HTTP 1.1 requests and responses from scratch, focusing on the underlying protocol mechanics. | |
| | | | |
enindu.com
|
|
| | | | | In a previous article, I provided a high-level overview of HTTP. In this article, I will dive into the low-level implementation of HTTP, covering topics such... | |
| | | | |
www.joeshaw.org
|
|
| | | I forget what I was told by myself | ||
