How to enable SSI’s in Apache

apache-2.2configurationserver-side-includes

I've found information on the web, but it just doesn't make sense to me. I'd like to know exactly what files I should go into, and precisely where and how I should modify them.

Best Answer

This has to be enabled (or the equivalent for your OS):

LoadModule include_module libexec/apache22/mod_include.so

And these added for the standard method:

AddType text/html .shtml
AddHandler server-parsed .shtml

#This one goes in the <Directory> directive you want them enabled for (ie "/")
Options +Includes

OR the --x bit hack:

XBitHack on

This last one allows you to keep the normal html name, but chmod o+x file.html and enable SSI just for that file(s).

Everyone else pointed to the old version of the documentation: Apache mod_include Docs

Related Solutions

Web-server – How to make Apache Web Server listen on two different ports

A standard Debian install of apache will have the following fragment of configuration:

Listen 80

<IfModule mod_ssl.c>
    # SSL name based virtual hosts are not yet supported, therefore no
    # NameVirtualHost statement here
    Listen 443
</IfModule>

This is telling apache to listen on port 80 and to listen to port 443 if mod_ssl is configured. In your case you'd want:

Listen 80
Listen 8080

You need to make sure you run a restart, not a reload operation on apache for it to pay any attention to new Listen directives. The safest thing to do is to stop apache, make sure it is dead and start it again.

If this configuration does not work, check the log files for any error messages. You could use "netstat -lep --tcp" to see if there is anything listening on port 8080. Finally, if everything else doesn't work, try running apache under strace to see if it's trying to bind to that port and failing, but not logging the problem.

Finding out what user Apache is running as

ps aux | egrep '(apache|httpd)' typically will show what apache is running as.

Usually you do not need to change the default user, "nobody" or "apache" are typically fine users. As long as its not "root" ;)

edit: more accurate command for catching apache binaries too

Best Answer

Related Solutions

Web-server – How to make Apache Web Server listen on two different ports

Finding out what user Apache is running as

Related Topic