2014-03-09 17:13
浏览 116


If a logged on user navigates to a certain area of the site which is to use WebSockets, How am I to grab that session Id so I can identify him on the server?

My server is basically an endless while loop which holds information about all connected users and stuff, so in order to grab that id I figured the only suitable moment is at the handshake, but unfortunately the handshake's request headers contain no cookie data:

Request Headers

Accept: text/html,application/xhtml+xml,application/xml;q=0.9,/;q=0.8
Accept-Encoding: gzip, deflate Accept-Language: en-US,en;q=0.5
Cache-Control: no-cache
Connection: keep-alive, Upgrade
DNT: 1
Origin: http://localhost
Pragma: no-cache
Sec-WebSocket-Key: 5C7zarsxeh1kdcAIdjQezg==
Sec-WebSocket-Version: 13
Upgrade: websocket
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0

So how can I really grab that id? I thought I could somehow force javascript to send cookie data along with that request but any self-respecting website in 2014 will have httpOnly session cookies so that wont work out. Any help is greatly appreciated!

Here's a download link for the files of the server I'm using

  • 点赞
  • 写回答
  • 关注问题
  • 收藏
  • 邀请回答

1条回答 默认 最新

  • dongping9475
    dongping9475 2014-03-09 19:02

    http only cookies as well as secure cookies work fine with websocket.

    Some websocket modules have chosen to ignore cookies in the request, so you need to read the specs of the module.

    Try: websocket node:

    Make sure to use the secure websocket protocol as wss://


    Also, chrome will not show the cookies in the "inspect element" Network tab.

    In node try dumping the request, something like:

     wsServer.on('request', function(request) {
       console.log(request.cookies); // works in websocket node

    If you see the cookies somewhere in the've got it.

    If you're using secure-only cookies, you need to be in secure web sockets: wss://


    The cookies are passed in the initial request. Chrome does not show it (all the time) as sometimes it shows provisional headers which omits cookie information.

    It is up to the websocket server to do 'something' with the cookies and attach them to each request.

    Looking at the code of your server: I do not see the word "cookie" anywhere, so it is not being nicely packaged and attached to each websocket connection. I could be wrong, that's why you might want to contact the developer and see if the whole header is being attached to each connection and how to access it.

    This I can say for certain: If you're using secure cookies then cookies will not be transmitted unless you use the secure websocket wss:// Plain ws:// will not work.

    Also, cookies will only be transmitted in the request if the domain is the same as the webpage.

    点赞 评论