Changes in p2_cli_http_headers.rs

a1a74d3a - WASIP3 HTTP return error for TooManyFields/TotalSizeTooBig (#12788)

Tue, 17 Mar 2026 01:53:14 +0000

WASIP3 HTTP return error for TooManyFields/TotalSizeTooBig (#12788)* WASIP3 HTTP return error for TooManyFields/TotalSizeTooBigReturn new error from* WASIP3 HTTP split tests between p2/p3p2 cases unchanged (they trap before break is reached).p3 cases assert the guest exited successfully and that it printed "error received", confirming the limit was actually enforced. List of files: /wasmtime-44.0.1/crates/test-programs/src/bin/p2_cli_http_headers.rs

511638f5 - Refactor `wasi:http` headers' host representation (#12754)

Tue, 10 Mar 2026 21:49:13 +0000

Refactor `wasi:http` headers' host representation (#12754)* Refactor `wasi:http` headers' host representationThis commit is a follow-on/extension of #12748 and extends the changesmade for WASIp2 headers in #12652 to the WASIp3 implementation as well.This is done through a number of refactorings to make the WASIp2 andWASIp3 implementations more similar in terms of how they representheaders. Changes here are:* `FieldMap` now has its own dedicated module at the crate root instead of intermingling with other WASIp2 types.* `FieldMap` is now internally-`Arc`'d and is cheaply clonable. `FieldMap` itself now tracks whether it's mutable or immutable (WASI semantics) and doesn't need different wrappers in WASIp2 and WASIp3.* Creation of an immutable `FieldMap` can be done without needing a size limit. Flagging a `FieldMap` as mutable, however, requires a size limit.* `FieldMap::set` was added to be a bit more efficient w.r.t. clones.* `FieldMapError` is a new error type that covers all of the possible error modes of operating with a `FieldMap`. Conversions from this to WASIp{2,3} `header-error` types are now implemented as well.* WASIp2 now flags `header-error` as a trappable-error-type, allowing the use of `?` in implementing header functions (like WASIp3).* Much of WASIp2's header implementation was refactored with `?`, moving methods around, shuffling where headers are made vs `FieldMap`, some minor idioms, etc.* WASIp3 no longer uses `MaybeMutable` for headers and instead uses `FieldMap` directly.cc #12674* Clippy warnings List of files: /wasmtime-44.0.1/crates/test-programs/src/bin/p2_cli_http_headers.rs

301dc716 - Fix two security advisories. (#12652)

Tue, 24 Feb 2026 18:23:59 +0000

Fix two security advisories. (#12652)* Fix two security advisories.This commit contains merged fixes for two security advisories inWasmtime:* GHSA-852m-cvvp-9p4w* GHSA-243v-98vx-264hThis introduces new knobs to Wasmtime to limit the scope of resourcesthat WASI implementations will allocate on behalf of guests. Unlikebackports to 41.0.x-and-prior these knobs all have default values whichare considered reasonable for hosts if they don't further tune them. Thefollowing CLI knobs have been added:* `-Smax-resources` - limits the total component-model resources a guest can allocate in a table* `-Shostcall-fuel` - a broad limit which enforces that at most this amount of data will be copied from the guest to the host in any one API call (e.g. `string` values can't be too big, `list` can't be quadratic, etc). This fuel is reset on each host function call.* `-Smax-random-size` - the maximal size of the return value of the `get-random-bytes` and `get-insecure-random-bytes` WASI functions.* `-Smax-http-fields-size` - a limit on the size of `wasi:http` `fields` values to avoid infinitely buffering data within the host.The `http` crate has additionally been updated to avoid a panic whenadding too many headers to a `fields` object.Co-authored-by: Mark Bundschuh Co-authored-by: Pat Hickey Co-authored-by: Joel Dice * CI fixes* Run rustfmt* Fix wasi-common build* Fix tests on 32-bit* Fix nightly test expectationsprtest:full---------Co-authored-by: Mark Bundschuh Co-authored-by: Pat Hickey Co-authored-by: Joel Dice List of files: /wasmtime-44.0.1/crates/test-programs/src/bin/p2_cli_http_headers.rs