Hi, at some point in the last couple months, wasmtime started allowing 600 as an HTTP response status. Is this intentional?
to clarify this is via the wasi:http/response#set-status-code method
this would appear to have happened via https://github.com/hyperium/http/pull/761
hm. not sure what the culprit is actually. i just know that setting 600 as status a couple months ago caused an error but is valid now :shrug:
I'm going to start returning those errors myself now
possibly 666
Yeah I think we updated the http crate dependency at some point which may have fixed this
HTTP status codes are supposed to be in the range 100...599. Based on how wasi:http generally adheres to standards I'd expect it to reject 600.
Last updated: Jan 10 2026 at 20:04 UTC