Thanks, Eddie. I'm in the process of redoing my secure pages. I'm ashamed that it took me a year to find out my mistake. Milton On Dec 18, 2005, at 2:21 AM, Eddie Hargreaves wrote: > .shtml is for Server Side Includes, and is not security-related. It > means > that the page contains links to html fragments that the server > includes when > the page is requested by the surfer. The 's' in front of the html > notifies > the server to look at the page for includes. But servers have to be > configured to permit server side includes, or SSI. Google SSI for more > information. > > > On 12/17/05 9:21 PM, Milton van der Veen > <miltonlist at hurontel.on.ca> wrote: > >> Thanks, Nick. Isn't it always the way when you finally ask a question >> that's been bugging you? I just noticed something about the >> pages ... I wonder if it's the extensions that are giving me the >> problems. >> >> I redid the page as "dot html" instead of "dot shtml" and it seems to >> work better. I've had them as "dot shtml" since I set it up a couple >> of years ago and I haven't had many complaints till the past month or >> so. (Maybe more people are using Firefox now.) >> >> There is really no reason to use the "dot shtml" extension is there? >> I had always thought that the "s" in front of the file extensions in >> a secure site was needed. Am I wrong?