According to the specification FastCGI supports responders, filters and authorizers. Nginx surely supports responders. I'm not sure, if it supports filters, but it definitely doesn't support authorizers. Is there a architectural reason behind it, was it simply forgotten, or wasn't it requested? We are interested in this feature! Unfortunately we don't have any C knowledge. FastCGI authorizers are necessary if you want to use nginx together with shibboleth. Cheers, -Tom Posted at Nginx Forum: http://forum.nginx.org/read.php?2,125679,125679#msg-125679
on 2010-08-31 17:16
on 2010-08-31 17:47
Hello! On Tue, Aug 31, 2010 at 11:15:24AM -0400, iT0m wrote: > According to the specification FastCGI supports responders, filters and > authorizers. Nginx surely supports responders. I'm not sure, if it > supports filters, but it definitely doesn't support authorizers. Is > there a architectural reason behind it, was it simply forgotten, or > wasn't it requested? > We are interested in this feature! Unfortunately we don't have any C > knowledge. FastCGI authorizers are necessary if you want to use nginx > together with shibboleth. FastCGI authorizers aren't supported (as well as filters), only responders. You may achieve similar effect by using auth request module, see here: http://mdounin.ru/hg/ngx_http_auth_request_module/ Maxim Dounin
Please log in before posting. Registration is free and takes only a minute.
Existing account
(Switch to SSL-encrypted connection)
NEW: Do you have a Google/GoogleMail or Yahoo account? No registration required!
Log in with Google account | Log in with Yahoo account
Log in with Google account | Log in with Yahoo account
No account? Register here.