Feature request:

Named pipe transport for FastCGI would help improve security and performance on Windows. Currently only TCP socket transport (address + port) is supported. Named pipe transport is of course for when the web server and fcgi app are running locally on the same machine. Apache supports this (Named Pipe on Windows, Domain Socket on *nix) and I believe lighttpd does as well.

The open source FastCGI library supports this mode of transport.
http://www.fastcgi.com


Thanks for your consideration!



Edited 1 time(s). Last edit at 03/28/2012 01:11PM by chef.

6 years later!

And this is the only reference to named pipes support for nginx's fastCGI module!