How nassim-hmdii/http_server works
This is a minimal POSIX-socket HTTP server. A client connects to the listener; the server receives and parses one request line, calls the response builder, sends its HTTP response, and closes that client connection. The builder selects the 200, 404, or 405 page and constructs status and headers, with a 500 fallback if a page cannot be opened. The graph reflects the README and shown source; it omits low-level socket calls as separate nodes and does not infer relationships beyond those documented or excerpted.
Main entry points: http.cpp Response builder · server.cpp Socket listener · 200-OK.html 200 page · 404-NotFound.html 404 page
Components 8
TCP server
- Socket listener
src/server.cpp - Request-line parsing
src/server.cpp
HTTP handling
- Response builder
src/http.cpp - HTTP response
src/http.cpp
Response pages
Other components
- HTTP client
Connections 8
- HTTP client → Socket listener: opens connection
README.md - Socket listener → Request-line parsing: parses request
src/server.cpp - Socket listener → Response builder: calls builder
src/server.cpp - Response builder → 200 page: reads for GET /
README.md - Response builder → 404 page: reads for other paths
README.md - Response builder → 405 page: reads for non-GET
README.md - Response builder → HTTP response: constructs response
src/http.cpp - Socket listener → HTTP client: sends response
README.md