Question

Scheme relative URLs (network-path references) are something that I’ve just found out about – where you don’t specify the scheme of a URL and it picks it up from the current context.

For example:
<img src="//example.com/img.png" /> will resolve to https://example.com/img.png if the current scheme is HTTPS or http://example.com/img.png if it is not.

This seems like a very easy way to resolve those pesky problems of calling an external script or image on an SSL page without bringing up the dreaded error that some content on a page is not secure.

The benefit seems obvious, but what I don’t seem to be able to find is a huge amount of information on this and was wondering if anyone had any experience or references about scheme relative URLs (good or bad)?

Whilst I’m trying to discover if there are any browsers that this causes issues with (I’ve been successful with IE6-8, Chrome and Firefox), I’m also interested to find out if anyone has any experience using this in different languages. For example, would it work if you were to issue a Response.Redirect with a scheme relative URL in ASP?

Answer 1

//example.com/img.png is a perfectly valid URI syntax as per RFC 3986: Section 4.2.

It is relative to the current scheme, and therefore as you mentioned, it can be very useful when switching between HTTP and HTTPS, because you won’t need to explicitly specify the scheme.

All modern browsers will understand that format, including IE 6.

Further reading on Stack Overflow:

• Is it valid to replace http:// with // in a <script src="http://...">?
• Using // in a <script>‘s source