title: Is a URL with // in the path-section valid?
body: <p>I have a question regarding URLs:</p>
  
  <p>I've read the <a href="http://www.ietf.org/rfc/rfc3986.txt" rel="noreferrer">RFC 3986</a> and still have a question about one URL:</p>
  
  <blockquote>
    <p>If a URI contains an authority component, then the path component<br>
    must either be empty or begin with a slash ("/") character.  If a URI 
    does not contain an authority component, then the path cannot begin<br>
    with two slash characters ("//").  In addition, a URI reference<br>
    (Section 4.1) may be a relative-path reference, in which case the<br>
    first path segment cannot contain a colon (":") character.  The ABNF<br>
    requires five separate rules to disambiguate these cases, only one of 
    which will match the path substring within a given URI reference.  We 
    use the generic term "path component" to describe the URI substring<br>
    matched by the parser to one of these rules.</p>
  </blockquote>
  
  <p>I know, that <code>//server.com:80/path/info</code> is valid (it is a schema relative URL)</p>
  
  <p>I also know that <code>http://server.com:80/path//info</code> is valid.</p>
  
  <p>But I am not sure whether the following one is valid:</p>
  
  <pre><code>http://server.com:80//path/info
  </code></pre>
  
  <p>The problem behind my question is, that a cookie is not sent to <code>http://server.com:80//path/info</code>, when created by the URI <code>http://server.com:80/path/info</code> with restriction to <code>/path</code></p>