No cookie set with connect-livereload

[darthcav]

No cookie set with connect-livereload

[Fishrock123]

@cavweb20 Are you doing SSL inside or outside of the node process? (if at all?)

Also, which version of cookie-session?

[darthcav]

@Fishrock123: It does not work either way, with or without SSL (I guess you mean HTTPS).

[Fishrock123]

Works for me with [email protected] and [email protected] -- can you try updating express and cookie-parser?

[darthcav]

I tried that already. Actual config is:

package.json:

...
        "body-parser": "1.0.2",
        "cookie-session": "1.0.2",
        "express": "4.1.2",
        "morgan": "1.0.1",
        "serve-favicon": "2.0.0",
...

application code:

...
var express = require("express");
var bodyParser = require("body-parser");
var cookieSession = require("cookie-session");
var favicon = require("serve-favicon");
var morgan = require("morgan");
...
app.use(morgan({ "stream" : access, "format" : "default" }));
app.use(express.static(app.get("public")));
app.use(favicon(path.join(app.get("public"), "images", "favicon.ico")));
app.use(bodyParser());
app.use(cookieSession({
        "name" : "sid",
        "keys" : [ "bla" ]
}));
...

environment:

export NODE_ENV=production

[raine]

I initially thought I have the same issue but seems that once you add a property to req.session the cookie is finally set.

app.use(function(req, res, next) {
  req.session.foo = 'bar';
  next();
});

Perhaps this is the intended behavior, although I was expecting a session to be created with some kind of unique identifier for the user in any case.

Also the README says,

If a session is new a Set-Cookie will be produced regardless of populating the session.

[raine]

I'm also noticing that when using Chrome to GET /, res.writeHead() doesn't get called thus not setting the cookies, meanwhile if I just curl http://localhost/index.html, writeHead() is called and cookies are sent.

edit: Why does Accept: text/html header prevent writeHead from happening?

[darthcav]

@raine: You are right, the cookie is only set when you write some parameter to the session. I don't think that it should be the expected behaviour, but I may be wrong.

[tiaozi0912]

@raine Do you define

app.use(livereload({port: livereloadport}));

before the cookie-session middleware? That caused me the issue same as yours

[dougwilson]

This is 100% a bug in connect-livereload module. it should never be doing this: https://github.com/intesso/connect-livereload/blob/v0.4.0/index.js#L94-L98 which will mess up a lot of things in node.js. you can track the fix for this over at intesso/connect-livereload#41