summaryrefslogtreecommitdiff
path: root/c/wasi-http/0.2.0/echo-request/wasi_snapshot_preview1.proxy.wasm (follow)
AgeCommit message (Collapse)AuthorFilesLines
2024-09-05w-h/0.2.0/echo-request: Update for wasmtime v24.0.0Andrew Clayton1-0/+0
It seems at some point between wasmtime v17 and v24 the setting of wasi_http_types_result_own_outgoing_response_error_code_t's val.ok member became mandatory. I was seeing an error like error: hyper::Error(User(Service), guest never invoked `response-outparam::set` method: error while executing at wasm backtrace: 0: 0x313b5 - wit-component:shim!indirect-wasi:http/types@0.2.0-[static]response-outparam.set 1: 0x4f9a - module.wasm!wasi_http_types_static_response_outparam_set 2: 0x6253 - module.wasm!exports_wasi_http_incoming_handler_handle 3: 0x54e4 - module.wasm!__wasm_export_exports_wasi_http_incoming_handler_handle Caused by: unknown handle index 0) Thanks to <https://github.com/cdmurph32> who it seems somehow found this code and had updated it accordingly. Link: <https://github.com/cdmurph32/pdf-text-example/blob/main/hello_world.c#L173> Signed-off-by: Andrew Clayton <a.clayton@nginx.com>
2024-02-06Add a wasi-http 0.2.0 echo-request component in CAndrew Clayton1-0/+0
This adds a WASI 0.2.0 version of c/wasi-http/echo-request, although there is no change in component.c, you do now need to link against the 'proxy' adaptor (which is included). This is for running under wasmtime 17. Signed-off-by: Andrew Clayton <a.clayton@nginx.com>