Changes in p3_http_proxy.rs

1cc0bcff - feat(p3)!: vendor 0.3.0-rc-2026-01-06 (#12250)

Tue, 13 Jan 2026 22:47:24 +0000

feat(p3)!: vendor 0.3.0-rc-2026-01-06 (#12250)* feat(p3)!: vendor 0.3.0-rc-2026-01-06Update wasmtime's WASI implementation from version0.3.0-rc-2025-09-16 to 0.3.0-rc-2026-01-06, using wkg for WIT vendoring.This involves API changes in clocks and HTTP.* Handle some review comments* Update WASI implementations to avoid `as`This can have a loss in precision so this shuffles around some types toensure that `try_into` and friends are always used instead of `as`. Thischanges the source-of-truth for timestamps to be `i64` seconds so WASIp2is the odd-one-out that can't represent negative timestamps.* Flag expected WASI failures* Get wasi:http tests working again* Rename `proxy` module to `service` to reflect the WIT world.* Adjust the middleware test to using the `middleware` world.---------Co-authored-by: Alex Crichton List of files: /wasmtime-44.0.1/crates/test-programs/src/bin/p3_http_proxy.rs

7e39c25e - move `ConcurrentState` from `ComponentInstance` to `Store` (#11796)

Mon, 06 Oct 2025 19:53:10 +0000

move `ConcurrentState` from `ComponentInstance` to `Store` (#11796)* move `ConcurrentState` from `ComponentInstance` to `Store`This has a few benefits:- No need to specify an instance when creating or piping from a stream or future.- No need to track the instance in an `Accessor`.- You may now execute tasks for multiple instances in a single event loop.The main drawback is that, if one of several instances within a single storetraps, it effectively means all instances have trapped, and the store can't beused to create new instances. The way to avoid that is to use separate storesfor instances which must be isolated from others.As a result of this change, a lot of code had to move from e.g. `impl Instance`to e.g. `impl StoreOpaque`, so the diff is pretty huge, but the changesthemselves are almost entirely non-functional.Fixes #11226Signed-off-by: Joel Dice * fix non-component-model-async buildSigned-off-by: Joel Dice * fix outdated doc commentSigned-off-by: Joel Dice * address review feedback- restore `ComponentStoreData` encapsulation- avoid conditional code duplication in `LiftContext::new`Signed-off-by: Joel Dice ---------Signed-off-by: Joel Dice List of files: /wasmtime-44.0.1/crates/test-programs/src/bin/p3_http_proxy.rs

ad027ea1 - check for host-body-wrapped-in-guest-body when creating requests (#11775)

Wed, 01 Oct 2025 17:56:58 +0000

check for host-body-wrapped-in-guest-body when creating requests (#11775)This is a follow-up to https://github.com/bytecodealliance/wasmtime/pull/11763,where we did this for responses, but I didn't think to do it for requests aswell. Now we do it for both, and test the scenario where a proxy componentforwards a inbound request body to an outbound request and then exits beforethat body has finished streaming, in which case the stream should continueflowing (assuming the embedder _wants_ it to).Signed-off-by: Joel Dice List of files: /wasmtime-44.0.1/crates/test-programs/src/bin/p3_http_proxy.rs