Module server

Expand description

Minimal HTTP server for RedDB management and remote access.

Modules§

handlers_admin: Lifecycle / admin HTTP endpoints (PLAN.md Phase 1).
header_escape_guard: HeaderEscapeGuard — typed boundary guard for HTTP response header values.
http_connection_limiter: Bounded handler-thread admission for the clear-text HTTP accept loop.
http_handler_metrics: Prometheus metrics for the HTTP handler-thread pool.
http_limits: Resolution of the three HTTP handler-pool knobs (issue #574 slice 5).
ingest_pipeline: JSON-first ingest pipeline — autodetects JSON-array bodies, NDJSON streams, and envelope-style payloads, then hands the rows over to the storage layer as a Vec<HashMap<String, Value>>.
tls: HTTP TLS termination for the embedded HTTP server.

HttpLimitsCliInput: CLI-layer input. Each pair holds the already-validated value coming from a flag and from an env var, respectively. The resolver applies the flag > red_config > env > default precedence using these inputs plus a config-store lookup.
HttpLimitsResolved: Resolved values after applying the full precedence chain. Stamped into both the RedDBServer and the startup log line.
RedDBServer
ServerOptions
ServerReplicationState: Replication state exposed to the HTTP server.

ServerSurface: PLAN.md Phase 6.2 — endpoint segregation. A given HTTP listener can serve either every public surface (Public, default) or a restricted slice (AdminOnly, MetricsOnly). The route filter at the top of route() consults this so a port bound only to loopback for admin work won’t accidentally hand out DML.