Now that I think about it, most (if not all) of my non-SSL links are in include files. So, it is easy enough to just place the full link in there. What bugs me is I've seen other sites with relative links on SSL pages that go to the non-SSL version (even when you hover over the link and your browser claims it is going to https). Using full links will be a pain too for maintaining production and development environments. Ugh...
It's easy enough to write a filter that notices https requests for resources that don't need to be protected, and redirects them to http. That kind of thing is certainly what the sites you mention are doing.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
