Stream: git-wasmtime

Topic: wasmtime / issue #14188 wasi-http v48 requires authority

view this post on Zulip Wasmtime GitHub notifications bot (Aug 21 2026 at 18:21):

ignatz opened issue #14188:

I have some code that proxies requests from an axum server to a wasm component. By upgrading to to v48, I'm now triggering: https://github.com/bytecodealliance/wasmtime/blob/main/crates/wasi-http/src/p2/types.rs#L92

The code is correct in: no authority is set, however previously this wasn't an issue. Is this WAI?

view this post on Zulip Wasmtime GitHub notifications bot (Aug 21 2026 at 18:34):

ignatz commented on issue #14188:

I noticed this only triggers when my server calls itself, i.e.:

client -> axum -> wasm-component ---(*)----> axum -> wasm-component

The request (*) has an authority set when I pass it to wasmtime_wasi_http::default_send_request to deliver it to localhost:

Request { method: GET, uri: http://127.0.0.1:4005/json, version: HTTP/1.1, headers: {}, body: UnsyncBoxBody }

but when axum receives it there's no more authority. The change in behavior may also stem from a change in wasmtime_wasi_http::default_send_request :woman_shrugging: . I'd love to provide a repro but I'm starting to get whiplash

view this post on Zulip Wasmtime GitHub notifications bot (Aug 21 2026 at 18:37):

ignatz commented on issue #14188:

https://github.com/bytecodealliance/wasmtime/blob/e6b33de5139d915a48127fc78b790e2d306cf896/crates/wasi-http/src/default_send_request.rs#L96-L98 sounds very relevant

view this post on Zulip Wasmtime GitHub notifications bot (Aug 21 2026 at 18:48):

ignatz commented on issue #14188:

I can confirm that when I add the schema+authority back (https://github.com/bytecodealliance/wasmtime/blob/e6b33de5139d915a48127fc78b790e2d306cf896/crates/wasi-http/src/default_send_request.rs#L96-L98), at surface level things go back to v47 behavior

view this post on Zulip Wasmtime GitHub notifications bot (Aug 21 2026 at 20:10):

tomasol commented on issue #14188:

This appears to be related to #14190 , can you try the fix in PR #14191 and confirm whether it resolves your scenario?

view this post on Zulip Wasmtime GitHub notifications bot (Aug 21 2026 at 21:58):

ignatz commented on issue #14188:

This appears to be related to #14190 , can you try the fix in PR #14191 and confirm whether it resolves your scenario?

Even w/o testing it the fix/workaround is clearly designed to appease:

https://github.com/bytecodealliance/wasmtime/blob/e6b33de5139d915a48127fc78b790e2d306cf896/crates/wasi-http/src/p2/types.rs#L90-L93

I'm more fundamentally puzzled by the statement:

at this point, the request contains the scheme and the authority, but the http packet should only include those if addressing a proxy, so remove them here,

The default_send_request method is saying: you gave me a request and I will change the request because I know better - why?

view this post on Zulip Wasmtime GitHub notifications bot (Aug 24 2026 at 15:38):

alexcrichton closed issue #14188:

I have some code that proxies requests from an axum server to a wasm component. By upgrading to to v48, I'm now triggering: https://github.com/bytecodealliance/wasmtime/blob/main/crates/wasi-http/src/p2/types.rs#L92

The code is correct in: no authority is set, however previously this wasn't an issue. Is this WAI?

view this post on Zulip Wasmtime GitHub notifications bot (Aug 24 2026 at 15:38):

alexcrichton commented on issue #14188:

I believe this was fixed in https://github.com/bytecodealliance/wasmtime/pull/14167 by accident sort of. This was indeed an accidental regression from https://github.com/bytecodealliance/wasmtime/pull/13812. Given that this should be fixed on main I'm going to close this. If I've mischaracterized this though please let me know.

Last updated: Aug 30 2026 at 09:07 UTC