Okay, well I can understand if it is considering the DTD when determing whether the content is secure. I guess I didn't realized that the dtd information ff the rendering xsl document would be considered. I do have an image on the page, but the image is coming from this secure site as well.
To be clear, I don't *know* that's a problem, but thought it might be a good place to 'test' and see if that's an issue. Can you place the DTD locally on the secure server and test? Then report back and let us know if it's a factor? That would be valuable info for us all. Someone on this list (who may be sleeping right now ;-p) might *know* whether or not this is an issue. I'm just hoping to give you an idea to test...
--
Clay Leeds - [EMAIL PROTECTED]
Web Developer - Medata, Inc. - http://www.medata.com
PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
