Page 1 of 1

Need SSI function, but can't change urls

Posted: Sun Oct 08, 2006 9:11 am
by keress
I have a large existing site I'm working on that gets good traffic that my client is heavily dependent on. I don't dare change his url's for fear the engines will drop his pages out of sight and his business will crash. I'd love to be able to use SSI's in the navigation structure, but can't afford to change the extensions of his files to .shtml. Also can't afford to change them to .php's. Is there some alternative method of achieving this function that will not involve changing urls?

Posted: Sun Oct 08, 2006 9:15 am
by timvw
Just configure apache to enable ssi/php for resources that end with .html (or whatever your client is using..)

Posted: Sun Oct 08, 2006 9:18 am
by keress
Thanks for the speedy reply. How do I do that?

Posted: Sun Oct 08, 2006 12:09 pm
by Ambush Commander
Research htaccess.

Posted: Mon Oct 09, 2006 1:12 am
by timvw
http://httpd.apache.org/docs/2.2/howto/ssi.html (And lookup the meaning of the AddType directive...)

Posted: Mon Oct 09, 2006 7:22 am
by keress
Thanks for the link. I found this one googling SSI htaccess: http://www.javascriptkit.com/howto/htaccess4.shtml. It mentions that there's a server drain if all .htm pages are read as SSI. Does anyone know if I should worry about it? My pages are now controlled by CSS, with very little coding on each page. Would each htm page being processed as SSI be more of a drain than the many lines of javascript I used to use to control navigation?

Posted: Mon Oct 09, 2006 9:30 am
by timvw
Comparing apples and oranges? JavaScript puts load on your client's machine... Enabling SSI on your webserver puts load on your server machine...