I'm starting to have flashbacks to the various C web CGI applications that I used to develop and maintain now... Awful is not the descriptor that I'd have used. These things were abominations, more so by todays "standards." I don't remember all of the details, but I do distinctly remember that user input was an absolute nightmare to deal with, as well as sending/receiving files.
Another nightmarish memory from those days: I once had a co-worker develop the backend to a web CGI in bash (!) and, before I knew he had done it, he was kicking it over the wall for me to finish. I ended up demonstrating why this would cause poor performance and then re-wrote it as C. Yikes. I'm really glad that we've moved beyond all of... that.
I did that once with Fortran 77 on Linux back in the 90's, but just as a joke. IIRC, there were some issues, like you could never suppress all of the console output it produced or something. In general, though, I think it's good to still have a lowbrow CGI option if you just want to throw something together.
Removing the parameters in the url gives a descriptive error page. (Error from Index+ Web Server (hixclient.exe)
I've found many museum sites running this.
I've had to maintain some of those.
https://en.wikipedia.org/wiki/Common_Gateway_Interface