Repository navigation
C-328: the full-response header set leaves out the nine client-managed fields on every lane - #137
Merged
Merged
Conversation
…der set on every lane, since a stock wasi:http host withholds them from a response Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
This was referenced Oct 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
C-328's p3 clause (als#133) promised that the full-response family reads the same lowercased header set on native and the stock WASI 0.3 component. That stopped holding on the host CI pins: wasmtime 49 withholds the client-managed fields from a response's fields, so
connection(andkeep-alive, …) vanish on p3 while native still shows them. almide/almide#3633 went red on exactly this (keys=content-length,…on p3 againstkeys=connection,content-length,…on native, CI wasmtime 49.0.1; locally wasmtime 47.0.2 passes them through, which is why it passed locally).The amendment
On every lane the header set leaves out the nine fields C-370 already names as client-managed (connection, keep-alive, proxy-authenticate, proxy-authorization, proxy-connection, transfer-encoding, upgrade, host, http2-settings — wasmtime-wasi-http's
DEFAULT_FORBIDDEN_HEADERS, identical in 47.0.2 and 49.0.1).get_header,header_valuesandheadersnever answer them.This narrows what native exposes rather than loosening the comparison: the alternative, excluding them from the comparison only, would leave a program that reads
connectionseeing it on native and not on p3.Implementation (almide/almide#3633, after this merges and the pin advances)
request_responseincrates/almide-rt-core/src/http_client_core.rsdrops the names inHTTP_FORBIDDEN_HEADERS;tests/http_response_cross_test.rsnow pins native's set without them and addsKeep-Aliveto the reply; it passes against wasmtime 49.0.1 and 47.0.2.Gates (local, all exit 0)
check-contracts, check-contract-provenance, check-als-element-coverage, check-als-style, check-als-validation, check-links, check-gate-verification, check-ratchet-separation --staged, selftest-conformance, check-runner-coverage; README / conformance regenerated (no change).
🤖 Generated with Claude Code
Replaces #135, rebuilt on main after #134 merged (the merge queue needs gates on the new base; no force-push).