The CGI protocol is a great way to map HTTP requests to system processes (environment variables, stdin, stdout, stderr and arguments). Using the same protocol we can map HTTP requests to WASI invocations.
### Tasks
- [ ] Recommendations for servers and example scripts
- [ ] Security considerations
- [ ] Add support for content encodings and prevent the script from changing headers necessary for communicating correctly with the client
- [ ] Add support for HTTPS scheme and expose the scheme to the script
- [ ] Non-Parsed Header script support
- [ ] Validate and improve URI encoding support and query param parsing
- [ ] Allow running CGI scripts from anywhere in the document root directory.
- [ ] Handle the PATH and PWD variables correctly for WCGI
- [ ] Handle non-UTF-8 header values
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
The CGI protocol is a great way to map HTTP requests to system processes (environment variables, stdin, stdout, stderr and arguments). Using the same protocol we can map HTTP requests to WASI invocations.
Documentation