Lighttpd

Will this be fixed in 1.5? If I use #include SSI directives I do not need to use PHP at all on my site, but not being able to send out the correct MIME type prevents me from doing this (in my case, I cannot use inline SVG without sending out an application/xhtml+xml MIME type).

-- evan

I just peeked at the code for mod_ssi.c and saw a line like this:

response_header_overwrite(srv, con, CONST_STR_LEN("Content-Type"), CONST_STR_LEN("text/html"))

Since it looked like lighttpd was just overwriting whatever header was previously there, I commented out the line and recompiled. Sure enough, lighttpd serves the correct MIME type for my pages now. I'm obviously not familiar with the lighttpd codebase, but it could be the case that this line was just thrown in during the initial coding of mod_ssi to get things working, and can now be safely removed.

I did the modification with 1.4.13, but the code for 1.5.0-r1691 (the latest release on the download page) is exactly the same.

-- evan

I have an XML file (content-type type application/xml) with server-side includes. It gets its content-type set to text/html which stuffs up the XSLT stylesheets since the browser gets the wrong type. I tried removing the offending line in mod_ssi.c that sets the content-type and now it is fine. Is there some issue with removing that line from the production source, since it has been suggested several times and nothing has happened?

Cheers,

Jan