Is there any downside for using a leading double slash to inherit the protocol in a URL? i.e. src=”//domain.com”

by

If the browser supports RFC 1808 Section 4, RFC 2396 Section 5.2, or RFC 3986 Section 5.2, then it will indeed use the page URL’s scheme for references that begin with “//”.

More Related Contents:

  1. Can I change all my http:// links to just //?
  2. URL without “http|https”
  3. What is the maximum length of a URL in different browsers?
  4. What is the difference between a URI, a URL and a URN?
  5. Escaping ampersand in URL
  6. http to https through .htaccess
  7. Can I use an at symbol (@) inside URLs?
  8. URL matrix parameters vs. query parameters
  9. Spaces in URLs? [duplicate]
  10. Why am I suddenly getting a “Blocked loading mixed active content” issue in Firefox?
  11. Dealing with HTTP content in HTTPS pages
  12. Easy HTTP requests with gzip/deflate compression
  13. Ideal HTTP cache control headers for different types of resources
  14. URL: Username with @
  15. Encrypt IDs in URL variables
  16. What is the difference between URI, URL and URN? [duplicate]
  17. Max memory usage of a chrome process (tab) & how do I increase it?
  18. Is a slash (“/”) equivalent to an encoded slash (“%2F”) in the path portion of an HTTP URL
  19. Are Callable Cloud Functions better than HTTP functions?
  20. URL hash is persisting between redirects
  21. HTTP and HTTPS iframe
  22. Add subdomain to localhost URL
  23. Reading cookies via HTTPS that were set using HTTP
  24. Semicolon as URL query separator
  25. Correctly switching between HTTP and HTTPS using .htaccess
  26. What is a safe maximum length a segment in a URL path should be?
  27. Is a URL with // in the path-section valid?
  28. What is the proper HTTP response to send for requests that require SSL/TLS
  29. HTTPS Proxy Server in node.js
  30. htaccess redirect for non-www both http and https

Leave a Comment