On 09 Jul 2001 15:24:59 -0400, Dale Ghent wrote:
>
> I just compiled .20 up from the tarball, and all seems great except when
> it comes to serving SSI (.shtml) pages.
>
> It looks like the SSI parsing goes okay, but the Content-Type header
> that's being returned is "text/plain" instead of the expected "text/html",
> thus causing the browser to show the page in it's source form.
>
Hi Dale,
I just pulled the latest CVS and I get text/html in the header.
My config
...
Options FollowSymLinks +Includes
...
AddType text/html .shtml
<FilesMatch "\.shtml(\..+)?$">
SetOutputFilter INCLUDES
</FilesMatch>
> I'm using the stock httpd.conf, with the SSI-related config container
> uncomented and "IncludesNoExec" added to the relevant directorie's
> Options. The shtml pages in question exist on a name-based vhost that's
> tacked onto the bottom of the config and has no directive in it that would
> seem to get in the way for SSI being read. The same config runs just fine
> on 1.3.x
>
> /dale
>
--
Ian Holsman
Performance Measurement & Analysis
CNET Networks - 415 364-8608
