Bug #1489: mod_fastcgi "/"-prefix extension issue - Lighttpd - lighty labs

Actions

Copy link

Bug #1489

closed

mod_fastcgi "/"-prefix extension issue

Added by icy over 16 years ago. Updated over 16 years ago.

Status:

Fixed

Priority:

Normal

Category:

mod_fastcgi

Target version:

1.4.19

ASK QUESTIONS IN Forums:

Description

A bug in mod_fastcgi.c prevents fastcgi settings with the /-prefix as extension not work properly in some situations.

Patch attached

Files

Download all files

mod_fastcgi.c.patch (594 Bytes) mod_fastcgi.c.patch		icy, 2007-12-17 18:22
mod_scgi.c.patch (578 Bytes) mod_scgi.c.patch	mod_scgi patch for same flaw	icy, 2008-01-16 00:00
mod_proxy.c.patch (940 Bytes) mod_proxy.c.patch	mod_proxy patch for same flaw	icy, 2008-01-16 00:01

Actions

Copy link

Updated by admin over 16 years ago

What situations?

Actions

Copy link

Updated by icy over 16 years ago

suppose one has a fcgi setting like the following:

fastcgi.server = ( "/fcgi.py" => (....) )

One would expect (having read the docs) that URIs like "/fcgi.py" or "/fcgi.py/foo/bar" are handled by the fcgi backend. That is true, but URIs like "/foo/fcgi.py" will also be forwarded to the fcgi backend because any fcgi extension setting using the /-prefix will match the internal check if it is at the beginning OR THE END of the URI.

The "/foo/fcgi.py" behaviour is contrary to what the docs say because it should ONLY match if at the beginning of the URI.

Actions

Copy link