-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is it possible to support fast cgi for Nginx? #42
Comments
I will happily look in to that but not sure what the ask is. Is there particular reason why you need fastcgi support? |
1 Nginx only support fast cgi, though I can install a cgi2fcgi gateway to bridge between them. |
I will happily look in to that but not sure what the ask is. Is there particular reason why you need fastcgi support? |
Actually the statement that fastcgi is more efficient than cgi is grossly misleading. It was true in the 90s for very busy sites / applications that ran on a small number of servers, which weren't scalable. No one is really developing apps like that any more. Nginx doesn't implement regular cgi (non-fast) service because there are no new cgi based applications made any more so why waste time implementing this. WFM was initially written in 90s specifically for Apache. It would be very very very hard to add FastCGI support to the existing WFM application, as is. It would be almost a complete rewrite. However so happens I'm actually rewriting WFM as a modern stand alone web app with it's own listener/server, and even auto cert manager. You can see it when you switch to "Go" branch under branches in Github. It's still not 100% complete but getting there. I already run it everywhere where I use WFM but it doesn't have all features of the previous version yet. FastCGI support is possible in the new upcoming version, not the legacy one. |
added support to head master it would be cool if you could test it and let me know thank you! |
Since Nginx support fast CGI, so would it possible to support fast cgi.
The text was updated successfully, but these errors were encountered: