Freepages-Help-L ArchivesArchiver > Freepages-Help > 2000-03 > 0952959967
From: "Leigh Compton" <>
Subject: Re: [FreeHelp] Server Side Includes on freepages?
Date: Mon, 13 Mar 2000 09:06:07 -0600
On 13 Mar 00, at 14:27, Rod Neep wrote:
> In article <>, Leigh Compton
> <> writes
> >SSI #include commands are a bit flakey on the Freepages server.
> >Randy has tried to find out why they aren't working correctly in all
> >cases and he's not been able to find the problem.
> >I've found that I can get them to work almost all of the time if I
> >use an empty HTML comment and a space just before the #include:
> ><!-- --> <!--#include file="filename.ext"-->
> Leigh... or Randy (if you have the time!)
> can you throw any light on the following:
> a. A .css file on /genealogy_html/common/style1.css
> cannot be called from /computers_html/index.htm
> using relative addresses.
> b. similar to the above with a .gif file (from genealogy)
> needing to be called in an html file in the computers directory
> (less of a problem, as I could use absolute addressing)
> having said that I did the shortcut by having the .css file and the
> graphics file in both directory systems... just that it seems a bit
> wasteful of disk space... (I still remember when my first hard disk
> was 1Mb <grin> so old habits die hard).
> Hey... I *asked* a question ;-)
The reason why a relative link doesn't work is that from the context
of the URL, these sites *appear* to be on different servers:
The insertion of your XXXXX_html directory name into the hostname
implies to the browser that these are completely different host
computers. The browser isn't able to conjure up a proper
hostname for its http request when you're trying to use relative
links across your directories.
The solution is to use a full URL (http://hostname/filename) instead
of relative links. Do css files not support full URLs? I've just
dabbled with them in the past, so I'm not sure what the restrictions
|Re: [FreeHelp] Server Side Includes on freepages? by "Leigh Compton" <>|