3 ms·
There's a huge difference: CGI is the ultimate backend in the HTTP stack, while this allows you to run scripts as middleware (ie modifying the response headers/
by rakoo 11y ago
There's a huge difference: CGI is the ultimate backend in the HTTP stack, while this allows you to run scripts as middleware (ie modifying the response headers/body based on previous processing)
- bmurphy1976 11y agoNot necessarily true. CGI could shell out to other CGI code if it wanted to. Turtles all the way down.
- rakoo 11y agoWhat if the backend is not CGI ? What if I want to use a script to gzip the output of a backend that doesn't compress anything ? Of course you can just call that backend through HTTP, but then you add another huge dependency on your little script that should just be as simple as "gzip -c -"