Bug #1489

mod_fastcgi "/"-prefix extension issue

Added by icy over 2 years ago. Updated about 2 years ago.

Status:Fixed Start:
Priority:Normal Due date:
Assigned to:- % Done:

0%
Category:mod_fastcgi
Target version:1.4.19
Missing in 1.5.x:

Description

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

Patch attached

mod_fastcgi.c.patch (594 Bytes) icy, 12/17/2007 06:22 pm

mod_scgi.c.patch - mod_scgi patch for same flaw (578 Bytes) icy, 01/16/2008 12:00 am

mod_proxy.c.patch - mod_proxy patch for same flaw (940 Bytes) icy, 01/16/2008 12:01 am

History

Updated by admin about 2 years ago

What situations?

Updated by icy about 2 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.

Updated by glen about 2 years ago

applied in r2030 for 1.4

Updated by glen about 2 years ago

  • Status changed from New to Fixed
  • Resolution set to fixed

Updated by glen about 2 years ago

  • Status changed from Fixed to Need Feedback
  • Resolution deleted (fixed)

Updated by glen about 2 years ago

  • Status changed from Need Feedback to New

Updated by glen about 2 years ago

Committed revision r2035.

Updated by glen about 2 years ago

  • Status changed from New to Fixed
  • Resolution set to fixed

Also available in: Atom