I used to encourage back-end web developers to write a web server from scratch as a learning exercise. With HTTP 1.1 it was actually pretty easy to write one in C (plus berkeley sockets); the idea being that you learn a lot about how things actually work at the lowest level without spending an inordinate amount of time. It's not really practical with HTTP 2 anymore but in any case, having done my own exercise I had no idea about many of these quirks.
The Rust Book has an awesome "final project" where it walks you through building a multi-threaded web server. If you're a battle-hardened C/C++ dev looking for an inroad to Rust, this is a great place to start.
Seems like you are the author of the book. Just wanted to say that this book makes me want to pick up Rust even though I have no specific goal for it, because the book is appealing in writing and appearance, layout and illustrations, ideas and execution.. basically good job and thank you!
I'm also here to worship your work! The Rust book is one of my favorite documentations around, and just the other day I sent it to a colleague who was interested in learning Rust. Even though he only had experience in Typescript and Java, he made a working chess engine less than three days later.
I also enjoyed the Rust Book. Thanks so much for the effort you and your co-author put into the book. And thank you for your contributions to the Rust language and tooling. I learned Rust over the difficult last year. It brings me some joy and satisfaction.
I teach web development and distributed systems in a local university, and one of my lab exercises is building an HTTP/1.0 Server in Python with sockets. I do have a blog post [1] that shows how to do it if someone's interested..
