HTTP Be wary of http/client.go Recently, I found out an interesting problem in Go. The problem can be reduced to a simple client request to a HTTP server. Suppose we have a HTTP server, which serves only one rooted path /foo/. package main import ( "io" "log&
HTTP HTTP/2 What is HTTP/2 and Why HTTP/1.1 has been serving most part of the Web since 1997. As websites get more and more sophisticated and resource intensive, it starts to show its limitations, e.g. one outstanding request per TCP connection. So