mod_fastcgi authorizers cannot protect fastcgi responders
lighttpd will serve a fastcgi as a static file if an authorizer is setup to protect its parent location.
if a fastcgi authorizer is setup to protect /test/
and a responder is setup at /test/test.fcgi, lighttpd will return the binary contents of test.fcgi (or a 404 if /test/test.fcgi is a remote responder).
This is because the mechanism to tell mod_fastcgi that it has already authorized a request never accounted for this need.
Updated by Anonymous almost 12 years ago
Where in the spec does it say that an authorizer can only protect static files? I just wasted an entire day writing an MySQL authorizer just to realize that LightTPD's implementation of the authorizer mode can only be used to protect static files and only if the mod_fastcgi matches URLs using file extensions. If URLs are matched using a path prefix, mod_fastcgi appends the prefix to the docroot and completely forgets about the rest of the URL. This so useless that I wonder why the authorizer support actually exists in mod_fastcgi. The attached patch looks sane to me, can't you apply it and get on with it? I don't really want to wait another year until 1.5 comes out, if at all.
Also available in: Atom