Why and how build your own web server in C#
summary
Concrete claim: a minimal C# web server runs on .NET both on Linux and Windows and actually serves requests (hello world demo) using a simple HTTP parser and file responses. It implements a middleware pipeline with modular middleware, enforces connection limits and overload policies (return 500 or drop), exposes an admin module on port 4040 with basic auth and a script endpoint, and uses an execution-context logger per module so logs remain correct and actionable.
AI-written summary · about
chapters (10)
- 0:00Introduction and Developer Journey
- 2:03Why Build Your Own Web Server?
- 4:00Understanding Web Server Basics
- 4:58Platform Challenges and Solutions
- 6:07Building the Web Server: Code Walkthrough
- 7:03Handling HTTP Requests and Responses
- 8:15Managing Connections and Middleware
- 17:06Administering and Operating the Web Server
- 25:27Logging and Execution Context
- 31:10Final Thoughts and Bonus Challenge
related talks
47mASP. NET Basics For Experts
20mEnterprise-Ready Minimal APIs in .NET: Scaling Simplicity
45m.NET for Linux and Windows
01h 01mThe Velvet Revolution: Dockerizing Legacy ASP.NET Apps
53mDemos are cool, but it is time to talk about the real world!
44mHow Real is this Cross Platform .NET Thing Really?
01h 26mDeep Web: A Web Cmdlets Deep Dive
32mBuilding and Running ASP.Net Applications in Habitat