Take the 2-minute tour ×
Webmasters Stack Exchange is a question and answer site for pro webmasters. It's 100% free, no registration required.

What does the double slash mean ? (I'm not referring to the beginning right after http:).

For example:

share|improve this question

3 Answers 3

up vote 22 down vote accepted

That is an error in the programmers'/developers' code.

For instance if you navigate to: http://www.imywebsite.gov/sectionA/sectionB/section/page/ And then add a slash: http://www.imywebsite.gov/sectionA/sectionB//section/page/

The exact same page will load in most modern browsers. This is something you want to fix. If you have the double slash it could confuse Google's web crawlers and make them think there is 2 versions of the page.

share|improve this answer
Actually, that the page loads has nothing to do with the browser, but rather that the server ignores the extra slash. This got long, so see the answer I posted. –  josh3736 Jan 27 '11 at 21:29

As mentioned by @RandomBen, the double slash is most likely the result of an error somewhere.

That the page loads has nothing to do with the browser, but rather that the server ignores the extra slash. The browser doesn't do anything special with extra slashes in the URL, it just sends them along in the request:

GET /sectionA/sectionB//section/page HTTP/1.1
Host: www.imysite.gov

It looks like current versions of Apache and IIS both will ignore the extra slashes while resolving the path and return the document that would have been returned had the URL not had extra slashes. However, browsers (I tested IE 8 and Chrome 9) get confused by any relative URLs (containing parent path components) of resources in the page, which produces bad results. For example, if a page has:

<link rel="stylesheet" href="../../style.css" type="text/css" />

Upon loading the page /a/b/c/, the browser will request /a/style.css. But if—for whatever reason—/a/b//c/ is requested (and the server ignores the extra slash), the browser will end up requesting /a/b/style.css, which won't exist. Oops, the page looks ugly.

(This obviously won't happen if the URL doesn't have a parent path component (..) or is absolute.)

It is my opinion that Apache and IIS (and probably others) are acting incorrectly as /a/b/c/ and /a/b//c/ technically represent two different resources. According to RFC 2396, every slash is significant:

  path          = [ abs_path | opaque_part ]

  path_segments = segment *( "/" segment )
  segment       = *pchar *( ";" param )
  param         = *pchar

  pchar         = unreserved | escaped |
                  ":" | "@" | "&" | "=" | "+" | "$" | ","

So, /a/b/c/ consists of three segments: "a", "b", and "c"; /a/b//c/ actually consists of four: "a", "b", "" (the empty string), and "c". Whether or not the empty string is a valid filesystem directory is a detail of the server's platform. (And logically, this means the browsers are actually operating correctly when parsing relative URLs with parent path components – in my example, they go up past the "c" directory and the "" directory, leaving us to request style.css from "b".)

If you're using Apache with mod_rewrite, there is a pretty simple fix:

# remove multiple slashes anywhere in url 
RewriteCond %{REQUEST_URI} ^(.*)//(.*)$ 
RewriteRule . %1/%2 [R=301,L] 

This will issue a HTTP 301 Moved Permanently redirect so that any double slashes are stripped out of the URL.

share|improve this answer
Wouldn't it be better to have your mod_rewrite solution take into account 3, 4, ... slashes too? Something along the lines of /{2,}? (Assuming Apache allows that kind of quantifier, I'm not too familiar with it) –  Ward Muylaert Jan 28 '11 at 0:16
+1 - Thanks for the extra info. I didn't think of it that way! –  RandomBen Jan 28 '11 at 11:18
It's not incorrect behavior: a/b and a//b indeed are two distinct URL paths, but nothing forbids the server from returning the same resource for both of them if it wants. I do agree with you, however, that in practice returning a 301 redirect would seem more useful. –  Ilmari Karonen Apr 9 '12 at 19:44
@IlmariKaronen: It absolutely is incorrect behavior because (1) this behavior automatically creates an infinite number of potential duplicate references to a single resource (which, if not in violation of the letter of any spec, certainly violates the spirit), and more practically (2) it "breaks" relative-path handling in browsers that do properly count the empty string in a//b as a directory (see the stylesheet example above). –  josh3736 Apr 9 '12 at 20:14
...and anyway, I'd argue that RFC 2396 does forbid a server from returning the same resource by auto-collapsing slashes because the spec says every slash is significant. Automatically ignoring consecutive slashes is in violation of that spec. (It's one thing if someone programmed their server to do that, even if doing so would be silly. However, servers doing this by default is incorrect.) –  josh3736 Apr 9 '12 at 20:21

The double slash has a meaning when it is used in resource URL's. For example, when it is user in CSS for an URL of a background image:

.classname {
    background : url("//differentdomainname/a/b/c/d.png");

Here it means this background image is fetching from a different domain other than the domain of the present web page. Or in other words, http:// can be written as just // when using that in resource URL's.

But this double slash in between the URL's (e.g.: /a//b/c/d.htm) doesn't have any meaning.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.