>>> [EMAIL PROTECTED] 07/28/00 12:12PM >>>
>The outermost frameset is called with a secure URL, and all of the <frame >src="..."> tags use only relative URIs. Nevertheless, when viewed on IE >the page gives the warning "this page contains both secure and insecure >elements" - it's not an IE specific bug, as Netscape's security summary >says the same thing - listing the individual page elements in Netscape >shows that it thinks that the html pages, all of which it correctly lists >as https://<whatever> have: You get this if ANY of the elements of the page (eg, images) are delivered
via an insecure method (http://, file://, etc). Make sure that *all*
images are delivered via HTTPS along with the HTML documents, and the error
should go away. The javascript ought not matter.
Hope this helps,
--Cliff
Cliff Woolley
Central Systems Software Administrator Washington and Lee University http://www.wlu.edu/~jwoolley/ Work: (540) 463-8089
Pager: (540) 462-2303 |
- Frames & Javascript -> insecure? Lee Feigenbaum
- Re: Frames & Javascript -> insecure? Cliff Woolley
- Re: Frames & Javascript -> insecure? Lee Feigenbaum
- Re: Frames & Javascript -> insecure? Doug Poulin
- Re: Frames & Javascript -> insecure? Paul