rmf*_*low 3 cookies session node.js express socket.io
我决定在我的应用程序中使用 socket.io 并偶然发现了一个问题。我用于cookie-session明确授权:
var session = require('cookie-session');
var app = express();
// ...
app.use(session({
keys: ['secretkey1', 'secretkey2']
}))
// ...
app.get('/settings', function(req, res) {
res.type("html");
if (!req.session.sid) {
console.log("NO SID");
req.session.sid = util.randomString();
}
else {
console.log("sid:" + req.session.sid);
}
// doing stuff with req.session.sid
var jadeView = { /*...*/ };
res.status(200).send(mainJade(jadeView));
});
Run Code Online (Sandbox Code Playgroud)
现在我使用socket.io。我弄清楚了如何访问cookie:
io.sockets.on('connection', function(socket) {
var cookie_string = socket.request.headers.cookie;
console.log("cookies: " + cookie_string);
// ...
}
Run Code Online (Sandbox Code Playgroud)
但是如何转换cookie_string为会话对象,就像在 中一样req.session?
@rmflow 2014 年的答案似乎不适用于 2017 年的socket.io-client 2.0.2 和cookie-session 2.0.0
显然,cookies包(cookie-session 的主要依赖项)需要一些不同的请求和响应对象。即请求对象应该有一个connection带有booleanencrypted属性的对象;此外,响应对象预计具有getHeader和setHeader方法。
const session = require('cookie-session')({
name: 'some-session-name',
secret: 'some-session-secret', // or an array of keys as usual
... // Other relevant options
});
io.on('connection', socket => {
let cookieString = socket.request.headers.cookie;
let req = {connection: {encrypted: false}, headers: {cookie: cookieString}}
let res = {getHeader: () =>{}, setHeader: () => {}};
//
session(req, res, () => {
console.log(req.session); // Do something with req.session
})
})
Run Code Online (Sandbox Code Playgroud)
| 归档时间: |
|
| 查看次数: |
3280 次 |
| 最近记录: |