3 ms·
It's slowcgi.. you know, as opposed to fastcgi. It's just a name. It was implemented so that httpd(8) didn't have to support executing CGI programs itself and c
by notaplumber 8y ago
It's slowcgi.. you know, as opposed to fastcgi. It's just a name. It was implemented so that httpd(8) didn't have to support executing CGI programs itself and could speak only FastCGI.
You don't /have/ to use it, but it's safer.
http://man.openbsd.org/slowcgi http://man.openbsd.org/slowcgi
- tannhaeuser 8y agoI was referring to the release announcement back in 2014 or so which I'm unfortunately not able to find (there was more than a bit snarkiness towards CGI programming). I'm aware what FastCGI is ;) Btw. if you're interested in native HTTP I'd be looking into nghttp2 rather than FastCGI and OBSD's httpd. Edit: see also https://ef.gy/fastcgi-is-pointless https://ef.gy/fastcgi-is-pointless and https://news.ycombinator.com/item?id=9202039 https://news.ycombinator.com/item?id=9202039 (previous discussion of OBSD's httpd)
- bigato 8y agohow can i trust a lib which still uses openssl in this day and age?