SSL Pad Lock Will Not Display

We have a web site where the SSL Lock will not display when you goto a secure
page using https. The page will display fine, but no Pad Lock. If you
right-click on the page and select "Properties |Certificates" It will show
the Cert information fine. I have also created a blank htm blank page, that
will display the ssl lock when accessed via https. None of the pages are
running in frames. The server is a Windows 2003 with IIS 6. The web site
pages are ASP and ASPX. I have contacted Verisign and they have looked at
the site and said the SSL is installed and working fine.

Any Ideas?

Re: SSL Pad Lock Will Not Display

"Sabatogz" wrote in message
news:7621AFA8-287A-4B68-B6D8-F04C2E3372E4@microsoft.com...
> We have a web site where the SSL Lock will not display when you goto a
> secure
> page using https. The page will display fine, but no Pad Lock. If you
> right-click on the page and select "Properties |Certificates" It will show
> the Cert information fine. I have also created a blank htm blank page,
> that
> will display the ssl lock when accessed via https. None of the pages are
> running in frames. The server is a Windows 2003 with IIS 6. The web site
> pages are ASP and ASPX. I have contacted Verisign and they have looked at
> the site and said the SSL is installed and working fine.
>
> Any Ideas?

There is a browser setting that allows the user to control if that lock
appears on secured sites.

Are you using the SAME BROWSER on the SAME MACHINE to test more than one
site?

What is the site? It helps if people can look at it.

Re: SSL Pad Lock Will Not Display

We have been using different browsers on different compters.

"Ratatooie" wrote:

>
> "Sabatogz" wrote in message
> news:7621AFA8-287A-4B68-B6D8-F04C2E3372E4@microsoft.com...
> > We have a web site where the SSL Lock will not display when you goto a
> > secure
> > page using https. The page will display fine, but no Pad Lock. If you
> > right-click on the page and select "Properties |Certificates" It will show
> > the Cert information fine. I have also created a blank htm blank page,
> > that
> > will display the ssl lock when accessed via https. None of the pages are
> > running in frames. The server is a Windows 2003 with IIS 6. The web site
> > pages are ASP and ASPX. I have contacted Verisign and they have looked at
> > the site and said the SSL is installed and working fine.
> >
> > Any Ideas?
>
> There is a browser setting that allows the user to control if that lock
> appears on secured sites.
>
> Are you using the SAME BROWSER on the SAME MACHINE to test more than one
> site?
>
> What is the site? It helps if people can look at it.
>
>
>

Re: SSL Pad Lock Will Not Display

We may have found the issue.

The SSL Padlock may not be displaying because there could be both secure and
non-secure pages in one document. Per other articles I have read is that
secure pages are still secure and the non-secure are not secure. The Padlock
is doing its job, by not displaying it's stating that not all the pages in
this document are secure.

I we respond once we make some changes to prove my point.

Re: SSL Pad Lock Will Not Display

Make sure to use relative paths for images, javascript, and other page
items. For example, to call an image called foo.jpg, use this:

/images/foo.jpg

Rather than

http://www.website.com/images/foo.jpg

If the browser is making a secure connection and determines that
ANYTHING might not be coming across the same HTTPS connection, it will
throw an error. In IE, the padlock will disappear and you get the
"This page contains secure and non-secure items". In Firefox, the
padlock has a diagonal slash through it.

Re: SSL Pad Lock Will Not Display

Issue Fixed.

I was correct, the page was pulling content from secure and non-secure
pages. Now that they are all secure "https:\\www.domain.com\my.html" We
have a padlock now.

"Sabatogz" wrote:

> We may have found the issue.
>
> The SSL Padlock may not be displaying because there could be both secure and
> non-secure pages in one document. Per other articles I have read is that
> secure pages are still secure and the non-secure are not secure. The Padlock
> is doing its job, by not displaying it's stating that not all the pages in
> this document are secure.
>
> I we respond once we make some changes to prove my point.