Rewrite std/net/http into a usable HTTP/1.1 server and client

[marcauberer]

What

Rewrites the std/net/http module from a non-functional stub into a usable, platform-independent HTTP/1.1 implementation, and adds tests.

The previous http.spice imported socket_linux directly (broken on other platforms) and had empty start()/serve() bodies. It is replaced with an implementation layered on the cross-platform std/net/socket abstraction.

Module

• HttpHeaders — insertion-ordered, case-insensitive header collection, so serialization is deterministic.
• HttpRequest / HttpResponse — value types you can build, serialize and parse. setBody keeps Content-Length in sync. Public data fields plus setHeader/getHeader/hasHeader helpers.
• parseHttpRequest / parseHttpResponse — socket-free parsers returning Result<...> (split on \r\n\r\n, tolerant of header whitespace/case).
• reasonPhrase(int) — canonical status text for common codes.
• HttpServer — addRoute(method, path, handler), handle() dispatch with a 404 fallback, and serveOnce / serveForever / stop over real sockets.
• HttpClient — send / get / post, auto-adding the Host header.

Drive-by fix

socket_windows.spice referenced SockLenT but never defined it (the Linux/Darwin variants do), which would block importing the socket layer — and now HTTP — on Windows. Added type SockLenT alias int;. Also updated std/README.md, which previously described HTTP as a libcurl-based client.

Tests

Test	Runs on CI?	Covers
std/net/http-messages	yes	request/response build + serialize (exact-byte asserts), parse, case-insensitive headers, header overwrite, reason phrases, round-trip
std/net/http-server-routing	yes	HttpServer.handle route dispatch + 404 fallback (socket-free)
std/net/http-server-client	disabled	end-to-end server+client over real TCP via a thread pool (mirrors existing sockets-basic)

The two runnable cases assert throughout and print one deterministic line, so their cout.out is just All assertions passed!.

Notes for reviewers

The message (de)serialization is intentionally socket-free and is what the runnable tests exercise. Two things worth a careful look since they lean on less-attested language usage:

• f<HttpResponse>(const HttpRequest&) used as a struct field (HttpRoute.handler) — procedure-pointer fields (p()) and f<...>(...) pointer params/locals are both attested separately in the tree, but the function-returning variant as a field is new here.
• The exact-byte serialization asserts in http-messages.

I was unable to compile locally in my environment, so this has been written/reviewed against existing std patterns but not executed. CI (or a local spicetest run) is the real check.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.