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? ... and I noticed that you used the "dot html" extension when you uploaded the file too. Milton On Dec 17, 2005, at 11:48 PM, Nick Scalise wrote: > On Dec 17, 2005, at 10:17 PM, Milton van der Veen wrote: > >> I look after a web site for Sleeping Children Around the World. We >> use PayPal for credit card donations and had to set up a sequence >> of secure pages on our web site to handle that. We use our ISPs >> secure server to save money. >> >> But I keep getting people using Firefox browser who tell me >> they're getting the HTML code in their browser instead of the >> rendered page. >> <https://host.zerowebhosting.com/scaw/secure/index.shtml> >> > > I went to the page in Firefox and got code. So I saved the file to > my harddrive and opened it in Firefox and it looked mostly as > expected (probably missing the style sheet). > > That would tell me that something is amiss on the server. > > If they say the page is coded correctly, ask them why code is being > displayed from the server. Correct code looks proper only if it is > served correctly. > > I placed the file on my cox space (hope that's OK, I will delete it > right away) and it works fine there... > > http://members.cox.net/nickscalise/scaw.html >