In this case, file:// is being treated as equivalent to http:// as far as
level of security goes. The only solution will be to move the images to
your web server and deliver them via HTTPS alongside the page itself.
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 >>> [EMAIL PROTECTED] 06/01/00 10:07PM >>> What do you mean by mixing up http and https. All of the images are called from a file. eg. src="file:///tmp/pic/images.gir" --would this be mixing up http and https. If yes, how do i overcome this problem. |
- Insecure information Mark Lo
- Re: Insecure information Albert Steiner
- Re: Insecure information Cliff Woolley
- Re: Insecure information Jody Fraser
- Re: Insecure information Mads Toftum
- Re: Insecure information Paul
- Re: Insecure information Mark Lo
- Re: Insecure information P.K.B. Hari Gopal
- RE: Insecure information Airey, John
- Cliff Woolley