<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">George N. White III wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAKTOP46L=MidRZ_7H50OnctJQx6OJpVtzAF9hv3R2jfFLrKLng@mail.gmail.com">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div dir="ltr">
<div class="gmail_quote"><br>
<div><br>
</div>
<div>For several years now, <a
href="https://www.paulirish.com/2010/the-protocol-relative-url/"
moz-do-not-send="true">Protocol Relative URL's </a> are
an anti-pattern to be avoided. </div>
</div>
</div>
</blockquote>
<br>
<br>
Not in my opinion. If a visitor establishes a non-secure link to my
site and seeks to fetch other resources from my site via embedded
links, those resources will be fetched insecurely; if he/she
establishes a secure link, then they will be fetched securely. If
I hard-code the links as HTTP, then those resources cannot be
accessed if the connection is secure; if I hard-code the links as
HTTPS, then I might well trigger the “This page contains both secure
and insecure Items” message from IE. Using protocol/schemeless URLs
is, to my mind, by far the best way to code local links when the
means of access (secure/insecure) cannot be known at the time of
coding.<br>
<br>
<br>
<blockquote type="cite"
cite="mid:CAKTOP46L=MidRZ_7H50OnctJQx6OJpVtzAF9hv3R2jfFLrKLng@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote">
<div> <br>
</div>
<div>As the above page notes, IE gives "<span
style="background-color:rgb(248,248,248)"><font style=""
face="arial, helvetica, sans-serif">“This Page Contains
Both Secure and Non-Secure </font></span></div>
<div><span style="background-color:rgb(248,248,248)"><font
style="" face="arial, helvetica, sans-serif">Items”
error messages.</font></span><br>
</div>
</div>
</div>
</blockquote>
<br>
You are reading something into that page that I cannot, George.
What the page notes is "If the browser is viewing that current page
in through HTTPS, then it’ll request that asset with the HTTPS
protocol, otherwise it’ll typically* request it with HTTP. This
prevents that awful “This Page Contains Both Secure and Non-Secure
Items” error message in IE, keeping all your asset requests within
the same protocol". Note, "THIS PREVENTS", not "THIS CAUSES".<br>
<br>
Philip Taylor<br>
</body>
</html>