Lighttpd

-- spam

I have the same problem.
Is it a bug or missconfiguring? Did this work on other versions?

Does anybody solved this problem?

We gave up and went back to apache we lost a week of migration downtime because of it. We have lhttpd on another server running static content and php index pages, its now 2% cpu load compared to 50%+ when apache was installed what a shame. Is lhttpd vaporware now ?

This bug seems to still be around in version 1.4.16. <!--#include virtual="test.php" --> doesn't parse the code, merely adds it as text.

-- nulani

Same problem here, Lighttpd does not parse included shtml, but inserts the code!

-- chris

problem still exists under 1.4.18. does anyone have any kind of solution?

-- Lightning

Replying to spam@electroteque.org:

<!--#include virtual="/cgi-bin/something.cgi" -->

It doesn't appear to run any extensions.

A poor manner run cgi with ssi is to use the exec directive

<!--#exec cmd="/usr/bin/php5-cgi /var/www/index.php" -->

But it is slow and not very clean, but it's the only way i success to do it.

-- petitchevalroux

Same problem here.

as of lighttpd-1.4.19 - Mar 26 2008 21:14:56 Still doesn't do it. We just use .cgi files for now, but it's a major pain as it breaks our normal ssi setup.

The same trouble here... Anyone resolved this problem? Problem exists in 1.5.x ?

I just installed lighttpd for the first time, from svn trunk, include virtua="/cgi-bin/myscript.pl" does not work. Uses the wrong path according to error log. If the cgi-bin exists in the document root as a sub directory, then it will include the file as plain text.

WTF!
Well, I think I found a solution:
The normal setup fails:
ssi.extension = ( ".shtml" )

But this worked!
ssi.extension = ( ".html", ".shtml" )

Would some one else please test this. I am using lighttpd 1.4.19(-r2) on Gentoo.
-DingbatCA

-- talbotx

Taken you long enough ! I think they worked something else out, like using php instead, I have no need for SSI personally but we were migrating from apache, so obviouslly there is an arrogance because the SSI feature is broken and not doing what its suppose to do. So why not just remove the module altogether. There is always technologies like AJAX anyway.

-- spam