Stream: wasmtime

Topic: http status 600


view this post on Zulip Andy Wingo (Dec 09 2025 at 10:46):

Hi, at some point in the last couple months, wasmtime started allowing 600 as an HTTP response status. Is this intentional?

view this post on Zulip Andy Wingo (Dec 09 2025 at 10:46):

to clarify this is via the wasi:http/response#set-status-code method

view this post on Zulip Andy Wingo (Dec 09 2025 at 10:50):

this would appear to have happened via https://github.com/hyperium/http/pull/761

Don't even need to feature-gate it or anything, this works on 1.49.

view this post on Zulip Andy Wingo (Dec 09 2025 at 11:08):

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:

view this post on Zulip Ralph (Dec 09 2025 at 13:55):

I'm going to start returning those errors myself now

view this post on Zulip Ralph (Dec 09 2025 at 13:56):

possibly 666

view this post on Zulip Alex Crichton (Dec 09 2025 at 15:21):

Yeah I think we updated the http crate dependency at some point which may have fixed this

view this post on Zulip Lann Martin (Dec 09 2025 at 16:23):

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