StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>See <a href="https://stackoverflow.com/questions/10161177/url-with-multiple-forward-slashes-does-it-break-anything">url with multiple forward slashes, does it break anything?</a>, <a href="https://stackoverflow.com/questions/11256190/are-there-any-downsides-to-using-double-slashes-in-urls">Are there any downsides to using double-slashes in URLs?</a>, <a href="https://webmasters.stackexchange.com/questions/8354/what-does-the-double-slash-mean-in-urls/8381#8381">What does the double slash mean in URLs?</a> and <a href="http://tools.ietf.org/html/rfc3986" rel="noreferrer">RFC 3986 - Uniform Resource Identifier (URI): Generic Syntax</a>.</p> <p>Consensus: browsers will do the request as-is, they will not alter the request. The <code>/</code> character is the path separator, but as path segments are defined as:</p> <pre><code>path-abempty = *( "/" segment ) segment = *pchar </code></pre> <p>Means the slash after <code>http://example.com/</code> can directly be followed by another slash, ad infinitum. Servers might ignore it, but browsers don't, as you have figured out.</p> <p>The phrase:</p> <blockquote> <p>If a URI does not contain an authority component, then the path cannot begin with two slash characters ("//").</p> </blockquote> <p>Allows for <a href="https://stackoverflow.com/questions/743247/types-of-urls">protocol-relative URLs</a>, but specifically states in that case no authority (<code>server.com:80</code> in your example) may be present.</p> <p>So: yes, it is valid, no, don't use it.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

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