wasi-http
wasi-http copied to clipboard
WebAssembly
Original context: https://github.com/WebAssembly/wasi-http/pull/3#discussion_r1122091615 There are certain pieces of metadata that are commonly associated with requests but aren't part of HTTP itself, e.g.: - Peer IP address - TLS session details...
From [this discussion on the v0.3 draft PR](https://github.com/WebAssembly/wasi-http/pull/101#issuecomment-1971968430) @lukewagner said: > https://github.com/WebAssembly/wasi-http/pull/103 is proposes adding a take-headers for extracting headers that become mutable (once they are disconnected from the request/response)....
If you try to generate bindings for 0.3.0 for C it fails: ```sh RUST_BACKTRACE=1 wit-bindgen c --autodrop-borrows yes ./wasi-http/wit-0.3.0-draft -w client thread 'main' panicked at crates/c/src/lib.rs:780:43: not implemented stack backtrace:...
### Preface Hi hi, I've been working with `wasi:http` a fair bit recently and have been enjoying it a lot. Thank you for that! Given we're currently still in a...
It could be worth further clarifying the drop & abort behaviours at various stages of the lifecycle of a request and response concretely, since these are observable implementation details in...
What is the expected/acceptable behavior in the host in terms of automatically setting the `Content-Length` header on behalf of the guest when the size of the body is known?
Closes #102. See discussion in that issue for the motivation and design of this change.
I failed to notice this was missing in #52. Status codes outside the range of 100-599 are [invalid](https://www.rfc-editor.org/rfc/rfc9110#section-15-6), though there is a nod to implementation-defined behavior outside those valid ranges....
Hi there, I'd like to bring attention to an area of ambiguity in the `wasi:http` specification concerning runtime behavior for incoming requests. Currently, implementations like `wasmtime serve` reinitialize the wasm...
The main case where this is currently painful is when trying to perform modifications while forwarding along an `incoming-request` as an `outgoing-request`, or `incoming-response` as an `outgoing-response`. The desired workflow...