I think this is a rather confusing article for beginners. I would say that request processing in an HTTP framework isn’t exactly a practical use case to demonstrate Go concurrency features. Most real-world applications are based on REST, which is stateless. In fact I would not associate HTTP server frameworks (in Go or in whatever language) with internal shared state management in an entry level article.
For people interested in Go concurrency features there’s this great curated list instead: