I'd like to resurface this issue on wasi-http metadata as it has recently come up again in the context of Spin's routing patterns.
Without a mechanism to pass this kind of information in the request itself you are stuck with either a parallel context interface or - historically the most popular path in HTTP systems - stuffing it into custom HTTP headers and (hopefully) correctly sanitizing those everywhere.
Last updated: Feb 27 2025 at 23:03 UTC