3 ms·
That was the original way (at least the most common way) to do CGI. Nginx as a reverse proxy / load balancer / SSL terminator / static file server pointing to a
by fgonzag 10y ago
That was the original way (at least the most common way) to do CGI. Nginx as a reverse proxy / load balancer / SSL terminator / static file server pointing to a backend running apache for mod_cgi or mod_fastcgi. And a lot of people would have both web servers running on the same server. You already have a web server, why do you need two?! Just pick one!
- ue_ 10y agoReverse proxying to Apache is still how I run my Perl CGI scripts. I'm not sure of a better way to do it that supports running multiple scripts.
- vidarh 10y agoI feel old now. It was nowhere near the original way - CGI predates Nginx by a decade. > why do you need two?! Just pick one! When they're good at different things.