…and not something else that happens to be 6-bytes long.

This is a first try at implementing CGI scripting. The idea is that, if CGI is explicitly enabled by the user, when a user requires an executable file instead of serving it to the client, that file will be executed and its output fed to the client. There are various pieces that are still lacking, the firsts that comes to mind are: - performance: the handle_cgi just loops ignoring the WANT_POLLIN/POLLOUT and blocking if the child process hasn’t outputted anything. - we don’t parse query variable (yet) - we need to set more variables in the child environment side question: it’s better to set the variables using setenv() or by providing an explicit environment? - document what environment the CGI script will get - improve the horrible unveil/pledge(cgi ? …) but now I can serve “hello-world”-tier script from gmid!

bad clients can shutdown the socket and we will exit due to a SIGPIPE. it ain’t fun.

make_socket can now return an ipv6 socket, and everything else still works. ipv4 is still hardcoded tho.

the ‘|| true’ idiom leads to better make error. Now the ‘-’ becomes a bit redundant tho…