
Systems 2026
c3web
HTTP/1.1, HTTP/2, HTTP/3, and WebSocket for C3.
c3web is an HTTP suite for C3: HTTP/1.1, HTTP/2, HTTP/3, and WebSocket, all running on c3io and libuv. It is a library, not a framework — it parses bytes, manages connections, and hands the application requests.
Conformance is the feature
It is easy to write an HTTP/1.1 parser that works against a browser and fails against a hostile client. c3web is written the other way around.
HTTP/1.1 is parsed incrementally, with streaming bodies, chunked transfer encoding and trailers, and explicit hardening: request-smuggling prevention, bare LF rejection, null-byte detection, size limits that produce 413 and 414, and version validation that produces 505.
HTTP/2 implements the framing state machine, the connection preface and SETTINGS exchange, HPACK with Huffman coding, stream multiplexing, and flow control with negative-window tracking. It passes the full h2spec conformance suite.
WebSocket implements RFC 6455 with fragmentation and reassembly, control frames, UTF-8 validation, the close handshake, and permessage-deflate. It is checked against the Autobahn test suite, with the remaining non-strict cases documented.
HTTP/3 is part of the suite, alongside the older protocols.
A server that fits a game loop
Because c3io never blocks, the same HTTP stack works in a request-serving process and in an application that polls the event loop once per frame. There is no hidden thread and no callback that takes over the program; the application decides when the network is serviced.