Note that there are some explanatory texts on larger screens.

plurals
  1. POHow do I get rid of the IE8 ssl warning message "Do you want to view only the webpage content that was delivered securely?” with ScriptManager?
    text
    copied!<p>A login page on our asp.net website uses https – while almost all of our other pages do not. On this login page, IE8 users receive the “Do you want to view only the webpage content that was delivered securely?” message. Many users press “Yes” out of habit which breaks our login page. I know the problem stems from the WebResource.axd and ScriptResource.axd script tags generated by ScriptManager.</p> <p>I’ve tried every method of referencing ScriptResource.axd/WebResource.axd – but no matter what I do I get the same IE8 warning – some examples:</p> <pre><code>&lt;script src='https://www.mysite.org/ScriptResource.axd?123' type="text/javascript"&gt;&lt;/script&gt; &lt;script src=' /ScriptResource.axd?123' type="text/javascript"&gt;&lt;/script&gt; &lt;script src=' //www.mysite.org/ScriptResource.axd?123' type="text/javascript"&gt;&lt;/script&gt; &lt;script src=' ../ScriptResource.axd?123' type="text/javascript"&gt;&lt;/script&gt; </code></pre> <p>Here is an example of a <a href="https://www.everyday-democracy.org/en/NoAxd.aspx" rel="nofollow noreferrer">simple page with no axd script (no IE8 prompt)</a> and <a href="https://www.everyday-democracy.org/en/OneAxd.aspx" rel="nofollow noreferrer">another page with the same markup and a single axd script (produces the IE8 prompt)</a>.</p> <p>Thinking there might be some strange redirection in iis for axd files - I’ve even tried response.redirecting axd requests to secure urls in global.asax. Application_BeginRequest with no effect.</p> <p>Does anyone know of a way to include the ScriptResource.axd/WebResource.axd scripts generated by script manager in a manner that does not trigger the "Do you want to view only the webpage content that was delivered securely?” IE8 message? Thanks!</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload