How tgomez-f/webserver-http works
WebServe is a configurable HTTP web server. Its principal workflow is accepting a client connection, receiving and parsing an HTTP request, selecting configured server/location behavior, then producing and sending a response; routes can also dispatch CGI requests. Configuration parsing, static-file handling, redirects, autoindexing, error pages, and CGI are represented as distinct product capabilities. The README contains references rather than an architectural description, and sampled source is incomplete; dashed, uncited edges mark relationships that are plausible but not verified as calls.
Main entry points: WebServ.cpp Event loop · StaticHandler.cpp Resource handler · Parser.cpp Config parser · Socket.cpp Listening sockets
Components 17
Configuration
- Config lexer
src/config/Lexer.cpp - Config parser
src/config/Parser.cpp - Virtual servers
src/core/Server.cpp - Route settings
src/core/Location.cpp
Network Runtime
- Listening sockets
src/core/Socket.cpp - Event loop
src/core/WebServ.cpp - Connection state
src/client/Client.cpp
HTTP Handling
- HTTP request
src/http/Request.cpp - Resource handler
src/http/StaticHandler.cpp - HTTP response
src/http/Response.cpp
Request Features
- CGI execution
src/cgi/Cgi.cpp - Error responses
src/utils/utils.cpp
Other components
- Server operator
- HTTP client
- Config file
- Served files
- CGI program
Connections 19
- Server operator → Config file: configures
- Config file → Config lexer: tokenizes
- Config lexer → Config parser: provides tokens
- Config parser → Virtual servers: builds
- Config parser → Route settings: sets routes
- Virtual servers → Listening sockets: defines listeners
- HTTP client → Listening sockets: connects
- Listening sockets → Event loop: serves events
- Event loop → Connection state: tracks connections
- Connection state → HTTP request: parses request
- Event loop → HTTP request: dispatches request
- Event loop → Resource handler: dispatches handling
- Resource handler → Route settings: uses route settings
- Resource handler → Served files: reads resources
- Resource handler → HTTP response: builds response
- Event loop → CGI execution: dispatches CGI
- CGI execution → CGI program: executes
- Event loop → Error responses: builds error response
- HTTP response → Connection state: sends response