Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Using javascript:OpenUrl() on SSL Causes "Mixed Content" Warning Dialog Box


View products that this article applies to.

This article was previously published under Q269682

↑ Back to the top


Symptoms

When you are using Secure Sockets Layer (SSL) and you click a link, you may receive the following warning message:
This page contains both secure and non secure items. Do you want to display the non secure items?

↑ Back to the top


Cause

This behavior can occur if the page contains links of the following form:
<A HREF="Javascript:Name()">
				
-or-
<A HREF="Vbscript:Name()">
				

↑ Back to the top


Resolution

To resolve this problem, obtain the latest service pack for Internet Explorer version 5.5. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
276369� How to Obtain the Latest Internet Explorer 5.5 Service Pack

↑ Back to the top


Workaround

To work around this behavior, use script code that is similar to the following sample code to disable the warning:
<SCRIPT LANGUAGE="JavaScript">
<!--
function OnClickHandler()
{ 
  var el=null;
  var flag=true;
  el = event.srcElement;
  // Do the While loop to find out if any of the parent elements 
  // are an A HREF.
  // This is necessary because in Internet Explorer 4.x, you can 
  // receive events of any element including the <B> tag.   
  while (flag && el)   
  {
    if (el.tagName == "A")
    { 
      flag=false;
      if (el.protocol == "javascript:")
      {
        execScript(el.href, "javascript");
        // A window.event.returnValue=false is performed so that the 
        // default action does not happen - which in case of an HREF
        // will be navigating to a link. 
        window.event.returnValue = false; 
      }
      if (el.protocol == "vbscript:")
      { 
        execScript(el.pathname, "vbscript");
        window.event.returnValue = false; 
      }
    } 
    else 
      el = el.parentElement; 
  } 
} // end OnClickHandler()

 document.onclick = OnClickHandler; // set the On click handler for the document 
//-->
</script>
				
Microsoft provides programming examples for illustration only, without warranty either expressed or implied, including, but not limited to, the implied warranties of merchantability and/or fitness for a particular purpose. This article assumes that you are familiar with the programming language being demonstrated and the tools used to create and debug procedures. Microsoft support professionals can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific needs.
If you have limited programming experience, you may want to contact a Microsoft Certified Partner or Microsoft Advisory Services. For more information, visit these Microsoft Web sites:

Microsoft Certified Partners - https://partner.microsoft.com/global/30000104

Microsoft Advisory Services - http://support.microsoft.com/gp/advisoryservice

For more information about the support options that are available and about how to contact Microsoft, visit the following Microsoft Web site:http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in Internet Explorer 5.5. This problem was first corrected in Internet Explorer version 5.5 Service Pack 1.

↑ Back to the top


Keywords: KB269682, kbqfe, kbie550sp1fix, kbfix, kbfaq, kberrmsg, kbbug

↑ Back to the top

Article Info
Article ID : 269682
Revision : 6
Created on : 11/23/2006
Published on : 11/23/2006
Exists online : False
Views : 348