Databases
StackOverflow2013
Postsdbo
POSocket.io via XHR-Polling not passing cookies
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSocket.io via XHR-Polling not passing cookies
    primarykey
    data
    text
    <p>I am attempting to combine Express (3.x) with NowJS (which is largely a wrapper around Socket.io) to create a real-time application that first requires that you log in. I'm admittedly new to Node, but I have a pretty good handle on how each package works separately. However, accessing Express Session information from NowJS is giving me fits.</p> <p>The problem seems to be that since I am forced to use XHR-Polling (using Heroku as a hosting platform), I am not able to easily access cookie information within the Socket.io authentication method. In the code below for authFunction, "data.headers.cookie" is undefined. In a roundabout way (within Now.js code), this is leaving "this.user.cookie" empty (but not undefined) in the nowjs.on("connect",...) callback. That in turn leaves me unable to grab the session information.</p> <p>From reading around, it seems like the cookie might only be available if using websockets. Without the cookie, I have no idea which user is making calls to the server other than a random identifier which gets generated for them.</p> <p>Can anyone suggest how to approach this? Do I need to manually send the cookie from the client side upon establishing connection to the Now.js server?</p> <pre><code>var app = express(); app.configure(function(){ app.set('port', process.env.PORT || 3000); app.set('views', __dirname + '/views'); app.engine('html', consolidate.swig); app.set('view engine', 'html'); app.use(express.favicon()); app.use(express.logger('dev')); app.use(express.bodyParser()); app.use(express.methodOverride()); app.use(express.cookieParser()); app.use(express.session({ secret: "secrethere" , store: sessionStore})); app.use(express.static(path.join(__dirname, 'public'))); app.use(app.router); }); app.configure('development', function(){ app.use(express.errorHandler({dumpExceptions: true, showStack: true})); }); //Map the routes var routes = require('./routes/routes')(db); app.get[...] //routes defined here var server = http.createServer(app, {cookieKey: 'connect.sid'}); server.listen(app.get('port'), function(){ console.log("Express server listening on port " + app.get('port')); }); var parseCookie = require('express/node_modules/connect').utils.parseCookie; var authFunction = function (data, accept) { // check if there's a cookie header if (data.headers.cookie) { // if there is, parse the cookie data.cookie = parseCookie(data.headers.cookie); // note that you will need to use the same key to grad the // session id, as you specified in the Express setup. data.sessionID = data.cookie['connect.sid']; } else { // if there isn't, turn down the connection with a message // and leave the function. return accept('No cookie transmitted.', false); } // accept the incoming connection accept(null, true); }; var everyone = nowjs.initialize(server, {socketio: {transports: ['xhr-polling', 'jsonp-polling'], authorization: authFunction}}); nowjs.on('connect', function (socket) { //TODO - This will need to be based on the URL that is being visited, or //similar to establish that users are viewing the same thing var sid = unescape(this.user.cookie["connect.sid"]); //# you DO have to unescape the session id! sessionStore.get(sid, function(err, sess){ console.log("That group who joined? his userId is " + sess.userId) }); var newRoom = "group";//this.user.session;//.groupName; var newGroup = nowjs.getGroup(newRoom); this.now.serverRoom = newRoom; newGroup.addUser(this.user.clientId); }); </code></pre> <p>edit: I would of course prefer simple solutions like the top answer here: <a href="https://stackoverflow.com/questions/9066834/session-support-in-now-js">Session support in Now.js</a>, but that does not work for me for (likely) the same reason - my "cookie" is empty and does not contain the "connect.sid" key.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. UScreativename
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSocket.io via XHR-Polling not passing cookies
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload