Menu
The Service Location Protocol (SLP, srvloc) is a service discovery protocol that allows computers and other devices to find services in a local area network without prior configuration. SLP has been designed to scale from small, unmanaged networks to large enterprise networks.
The iterable protocol allows JavaScript objects to define or customize their iteration behavior, such as what values are looped over in a for...of construct. Some built-in types are built-in iterables with a default iteration behavior, such as Array or Map , while other types (such as Object ) are not.
I want to construct URLs with the same scheme (presumably, "http:" or "https:") as the page that loaded the currently-running JavaScript. Modern browsers support simply omitting the scheme (for example, src="//example.com/test.js"), but this isn't fully cross-browser compatible. (I've read that IE 6 is the only browser that doesn't support it, but I still need compatibility with that version.)
The cross-browser way to do this seems to be to check location.protocol. For example, Google Analytics uses:
('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + ...
In Google's case, they wanted to use different domains depending on whether the request uses SSL, so that pattern makes sense. But I've seen others use the same pattern even when only the protocol is different:
('https:' == location.protocol ? 'https:' : 'http:') + "//example.com"
(One example is in the "Final Wufoo Snippet" at http://css-tricks.com/thinking-async/.)
I'd prefer to use this simpler expression instead:
location.protocol + "//example.com"
Should I really be concerned about the possibility of location.protocol taking on some value other than "https:" or "http:" when my code is used on sites I don't control?
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With