>the head?
Ah, now I understand your problem. If you use relative pathing for all of your client-side references, when you call a page using SSL, everything will be encrypted. If you call images or CSS files using fully qualified URL's, you will need to make sure the URLs are correctly set either to use SSL or not depending on the situation. You can use application-wide variables for secure and non-secure base URLs to accomplish that.
One possible problem I see with what you are setting up is that use of SSL is generally enforced at the directory level, but you don't indicate that you are segmenting your site to require SSL in any particular area of the site. If you want to enforce SSL in certain areas of your site, you will need to segment those areas into separate directories from the rest of the site and require SSL for access to those files.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
