Bug #1489

mod_fastcgi "/"-prefix extension issue

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

Status:FixedStart date:
Priority:NormalDue date:
Assignee:-% 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 Magnifier (594 Bytes) icy, 2007-12-17 18:22

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

mod_proxy.c.patch Magnifier - mod_proxy patch for same flaw (940 Bytes) icy, 2008-01-16 00:01

History

#1 Updated by admin over 6 years ago

What situations?

#2 Updated by icy over 6 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.

#3 Updated by glen over 6 years ago

applied in r2030 for 1.4

#4 Updated by glen over 6 years ago

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

#5 Updated by glen over 6 years ago

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

#6 Updated by glen over 6 years ago

  • Status changed from Need Feedback to New

#7 Updated by glen over 6 years ago

Committed revision r2035.

#8 Updated by glen over 6 years ago

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

Also available in: Atom