Bug #321


mod_fastcgi authorizers cannot protect fastcgi responders

Added by Anonymous over 18 years ago. Updated over 7 years ago.

Target version:


lighttpd will serve a fastcgi as a static file if an authorizer is setup to protect its parent location.

For example,
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.

-- cpisto


fastcgi-authorizer-fixes.diff (6.61 KB) fastcgi-authorizer-fixes.diff All fastcgi mode=authorizer fixes (Variable- env works, proper re-dispatching, and assert failure fix when auth is running in front of cgi). maherb, 2006-06-20 12:02
Actions #1

Updated by maherb about 18 years ago

This seems like a pretty important detail, and if you are going to advertise the fact that you support a fastcgi authorizer, you should probably warn users about this defect .

Actions #2

Updated by maherb over 17 years ago

  • Status changed from New to Assigned
Actions #3

Updated by jan almost 17 years ago

  • Status changed from Assigned to Fixed
  • Resolution set to invalid

We are only following the FastCGI spec.

In 1.5.0 we added X-Rewrite which fixes this is a generic way.

Actions #4

Updated by Anonymous over 16 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.

Actions #5

Updated by stbuehler over 15 years ago

  • Status changed from Fixed to Invalid
Actions #6

Updated by gstrauss over 7 years ago

  • Description updated (diff)
  • Status changed from Invalid to Patch Pending
  • Target version set to 1.4.42
Actions #7

Updated by gstrauss over 7 years ago

  • Status changed from Patch Pending to Fixed
  • % Done changed from 0 to 100

Also available in: Atom