fix cookies import when create the websocket

[hschouman]

The upgrade to web socket should import only cookies relative to the url.
Without this specify, all cookies are imported and in my case it never upgrade to web socket (because there are several cookies in header that does not match the session)

[hschouman]

For more information on my use case with cookies here, I use session affinity on heroku :
https://devcenter.heroku.com/articles/session-affinity

But I guess there are other use cases with cookies here

[nuclearace]

Hm, the idea for this was to allow cookies from the initial polling connection to carry over to the websocket connection.

[hschouman]

Sure and you only want the cookies relative to the current connection/url or I miss something ?

[nuclearace]

@hschouman Have you tested if this ever actually returns cookies? There's a scheme difference between urlWebSocketWithSid and urlPollingWithSid, and session will only ever have the polling url.

[hschouman]

You are right. In my case I have the same result with the two schemes because the cookies are stored with the base url (path == "/").
I've just fixed that.

[nuclearace]

@hschouman One last thing, can you change this to be opened against development?

[OneSman7]

Found this after made comment in my PR #1058 (#1058 (comment)).
This PR also fixes bug described there. It is only left to decide whether it will be better to pass filtered cookies to addHeaders method or to filter them by domain inside addHeaders method.