<p>http.Response.Cookies() is returning an empty list, but the Response carries a 'Set-Cookies' header with valid data. Also, the CookieJar isn't catching any cookies either:</p>
<pre><code>fmt.Println("Set-Cookie:", strings.Join(rsp.Header["Set-Cookie"], " | "))
fmt.Println("Cookies(): ", rsp.Cookies())
fmt.Println("Jar: ", jar)
</code></pre>
<p>Output:</p>
<pre><code>Set-Cookie: express:sess=eyJwYXNzcG9ydCI6e30sImZsYXNoIjp7fX0=; path=/; httponly | express:sess.sig=QSHjYGweA7mxUoPNgmgRcJxY8Ws; path=/; httponly
Cookies(): []
Jar: &{<nil> {0 0} map[] 0}
</code></pre>
<p>I'm sure I'm doing something wrong, I just can't spot the problem. Thoughts?</p>
<p>EDIT: It appears that Go's HTTP stack doesn't consider ExpressJS cookie names to be valid, but it's not clear to me why not. I pulled out the relevant bits of the HTTP cookie parsing stack to produce this demo, but I still don't understand why these cookie names aren't considered to be valid:</p>
<p><a href="https://play.golang.org/p/13g728UPkF" rel="nofollow">https://play.golang.org/p/13g728UPkF</a></p>
<hr/>**评论：**<br/><br/>barsonme: <pre><p><code>:</code> is not valid inside a cookie name. It is a separator. You can read about it in the RFC: <a href="https://tools.ietf.org/html/rfc2616#section-2.2" rel="nofollow">https://tools.ietf.org/html/rfc2616#section-2.2</a></p></pre>weberc2: <pre><p>That answers my question. Thanks!</p></pre>
