Matthew Hannigan wrote:
On Fri, May 08, 2009 at 02:25:13PM +1000, david wrote:
Matthew Hannigan wrote:
On Fri, May 08, 2009 at 01:13:39PM +1000, Rob Weir wrote:
On 8 May 2009, [email protected] wrote:
I've got this snippet in apache config:
<Directory /var/www/test/>
Options +Includes XBitHack full IncludesNOEXEC
</Directory>
da...@david:/etc/apache2$ sudo /etc/init.d/apache2 reload
Syntax error on line 17 of /etc/apache2/sites-enabled/000-default:
Illegal option XBitHack
...fail!
da...@david:/etc/apache2$
mod-include is enabled
Are you /sure/?
Innit mod_ssi ?
I'm not sure what this should do.. I'm using Ubuntu/Debian which uses
a2enmod to set up modules, followed by apache2 reload. Am I missing
something?
thanks...
I was pointing out that XBitHack is part of mod_ssi, not mod_include.
Is it???
http://httpd.apache.org/docs/2.0/mod/mod_include.html
seems to suggest mod_include ... although I'm often wrong and I might be this
time.
As for what it does; well what do you want it do do?
What I want to do is server side includes. I have another production site where
this works perfectly, but uses the .shtml suffix and AddOutputFilter. It would
be nicer if I could use XBitHack but for some reason the apache2 parser doesn't
like it.
By putting this line:
AddOutputFilter INCLUDES .html
on my test site's /etc/apache2/mods-enabled/mime.conf the includes magically
work as advertised, but that's not really what I want. The whole idea is to only
parse for includes when required instead of every html page.
I'd take it out if you're not sure.
I'm sure what I want to do.. see above.
SSI (server side includes) can
make the security of apache a little more fragile.
because??? Perhaps there is a good reason not to do it. I've got the
IncludesNOEXEC option happening.
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
