Bug#501354: Regression in FastCGI path handling in 1.4.13-4etch11 security upload

2008-11-15 Thread Chris Lamb
(Please ensure you CC the submitter next time; your response has been sitting on the BTS for over a month now as I had not been notified there was any update. :/) Olaf wrote: For example, visiting /foo would result in the application (NB. not the webserver) reporting a 404 at

Bug#501354: Regression in FastCGI path handling in 1.4.13-4etch11 security upload

2008-11-15 Thread Olaf van der Spek
Chris Lamb wrote: (Please ensure you CC the submitter next time; your response has been sitting on the BTS for over a month now as I had not been notified there was any update. :/) The BTS should be fixed to do that automatically. ;) Olaf wrote: For example, visiting /foo would result in

Bug#501354: Regression in FastCGI path handling in 1.4.13-4etch11 security upload

2008-10-06 Thread Chris Lamb
Package: lighttpd Version: 1.4.13-4etch11 Tags: security Hi, When upgrading from 1.4.13-4etch10 to 1.4.13-4etch11, I noticed that my FastCGI applications were not being passed the correct path. For example, visiting /foo would result in the application (NB. not the webserver) reporting a 404 at