dickbaker - 4:12 am on Sep 26, 2008 (gmt 0)

Thanks for being so patient with me, Tedster.

My hosting company said that they could set up the secure.example.com subdomains as you describe.

However, I don't see how that addresses the problem of my non-secure pages showing up with both the http and https protocols. I haven't been able to find a workable robots.txt solution to disallow the https prefix.

Can you or anyone else think of a direction to point me to?

Thanks for your patience.