Msg#: 3137449 posted 11:07 pm on Oct 27, 2006 (gmt 0)
Try using *NIX symlinks (symbolic links), for example, symlinking a "new" secure css directory to the pre-existing non-secure css file directory. You can then force SSL on the new secure directory, which will appear to contain copies of the symlinked files. Not ideal, perhaps, but it prevents having to have real copies of the files in two directories.
Msg#: 3137449 posted 4:03 am on Nov 4, 2006 (gmt 0)
I used to run into this problem consistently and finally I found something that worked.
On on of my secure sites, lets say https://www.example.com/htaccess/ I wanted to give my visitors the option to post youtube videos and google videos. But then everyone kept seeing the "warning, mixed secure/non-secure content" on a page that had one of these videos.
I basically did a str_replace on all posts text for [video.google.com...] and [youtube.com...] to change them to https://www.example.com/htaccess/
Msg#: 3137449 posted 9:25 pm on Nov 12, 2006 (gmt 0)
If you have your ssl virtualhost in your Appache config file pointing to the same document root as the non-ssl virtualhost for that domain then it should be able to serve any file from that directory as ssl or non ssl, I think. I may be mistaken though but it works for me...