Closes mcpplibs#15 and mcpplibs#16. Version 0.3.0. mcpplibs#16 first, because it has to be. A write to a socket whose peer has gone away raises SIGPIPE, and a program that has not disarmed it — the default — is killed rather than told. The fd is one this library created and the write is usually the close_notify its own pool clean-up sends, so this is the library's defect. mbedtls guards against it in net_prepare with a process-wide signal(SIGPIPE, SIG_IGN); replacing mbedtls's network layer with a custom BIO dropped that guard and put nothing in its place. MSG_NOSIGNAL, and SO_NOSIGPIPE where that does not exist, is the better replacement anyway: a library has no business changing its host's signal disposition, and a program that wants SIGPIPE on its own stdout still gets it. Which of the two applies is decided by the target's own <sys/socket.h> and by nothing else — measured: glibc and musl carry MSG_NOSIGNAL and not SO_NOSIGPIPE, Darwin the reverse, Windows neither and no signal to raise. P0 had to land before everything else here, because everything else makes the drop path more common. Then mcpplibs#15. It named two of the eleven paths that could leak a connection; all eleven are fixed. Four of the other nine turned up while verifying the report — a redirect, a non-2xx and a failed file open, none of which involve a timeout or a truncation at all, plus a Content-Length past 32 bits — and two more were regressions 0.2.10 had introduced into the streaming reader. Every one of the eleven has the same shape: an early-return path that did nothing, where doing nothing left a socket with unread bytes in the pool for the next request to pick up. So dropping is now what doing nothing means — a PooledConnection guard whose destructor drops, and one call to keep() on the single path where the body was read to the end its framing declared. The reason there were eleven rather than one is that send, send_stream and download_to_file each carried a near-copy of the status-line parse, the header loop and the body loop, and every past hardening had landed on one or two of the three. mcpplibs#14 is the most recent example: it added a Content-Length branch to one copy and introduced two regressions doing it. There is now one status-line parser, one header reader and one body reader. read_body returns where the body ended, and that is the same question as whether the connection can be reused. Two further unbounded loops found while writing that reader, neither reported: a header block accumulates into a map, so an endless supply of short, well formed header lines grows the client's memory without limit; a trailer section is discarded but holds the call open just as long, because every line resets the read timeout. Both are bounded now, as each line's length already was. Added, all of it additive: HttpResponse::bodyComplete and bodyError, because a truncated 200 and a complete 200 were indistinguishable to the caller; ok() does not consult them, so existing code means what it did. maxResponseBodyBytes, because the size send() was about to allocate came from a header. retryOnStaleConnection, because a server closing an idle keep-alive connection is routine and the client cannot see it until it writes — that failure reached callers as "No response" for a request the server never saw. The window is one attempt, on a pooled connection, before a single response byte has arrived. tests/ had no keep-alive coverage at all, which is why mcpplibs#14's regression merged green. It now scripts an in-process TLS server — the library speaks only HTTPS, so a plain listener cannot reach the code under test — and every pool test asserts how many TCP connections the server saw as well as what came back. The report for mcpplibs#15 contains a case whose output is byte-for-byte correct and whose only symptom is the connection count. Each fix was checked by mutation. Three tests did not survive that and were rewritten: the SIGPIPE child stopped at its first failed write, which returns ECONNRESET without a signal; and the pool servers stalled rather than sending their remaining bytes, so the connection was silent rather than dirty and the stale-connection retry rescued the second request whether or not the guard worked. Two more found by review after the above was written, one of them introduced by it. Reading past a 1xx is new: a 103 Early Hints or a 100 Continue was returned to the caller as the answer, and — once a 1xx counted as a response with no body — the connection was marked clean with the real response still sitting on it, which is mcpplibs#15 arriving by another door. And the BIO answered a peer's FIN with MBEDTLS_ERR_NET_CONN_RESET where mbedtls's own passes the zero through, so `ssl_fetch_input`'s test for exactly that zero (ssl_msg.c:2251) never fired; a body whose framing IS the close then read as truncated, and download_to_file reported ok() == false for a file that had arrived complete. Also here, because all three are about the same claim — that this library works where it says it does: examples/openkal builds these sources above openkal, the portable kernel ABI, and makes a real HTTPS request through kal_net_connect. It is a separate CI job because whether MSG_NOSIGNAL or SO_NOSIGPIPE exists is decided by the C library rather than the operating system, and a #ifdef that is wrong about that compiles cleanly on the gcc job and fails there — which is how 5e7d66f reached master. templates/ ships three starting points for `mcpp new --template tinyhttps`, one per entry point. tools/template_smoke.sh renders and builds them against the working tree, because `mcpp new` can only reach a template that is already published, and checking them after the release makes the first user the one who finds out. It has already caught one: import std carries no stdout macro, so a progress bar flushed through it compiled here and not in a generated project. mcpp.lock is removed and ignored. The file's own header says it does not pin anything — "index dependencies are re-resolved from their constraints each time" — so for a library, whose consumers resolve from its constraints, it recorded one machine's resolution and changed nothing about anyone else's. Eight of the ten mcpplibs packages already ignore it, the scaffold template among them.

Breadcrumbs

User selector

Datepicker

Commit history

Commits on Sep 5, 2026

Make the pool's invariant the default, and stop the library killing its host (#17)

Commits on Mar 15, 2026

feat: add download_to_file with streaming progress callback

Commits on Mar 10, 2026

feat: initial release of mcpplibs-tinyhttps