blocks|key|1043089|text|你可以看看这个：https://github.com/bmeck/session-web-sockets|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1043090|或者，您也可以使用：|1043091|io.on('connection',+function(client)+{+
++var+session+=+client.listener.server.viewHelpers;+
++//+use+session+here+
});|code-block|syntax|javascript|1043092|希望这能有所帮助。|1043093|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/bmeck/session-web-sockets^0|8|18|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|Z|8|@]|9|@]|C|$I|J]]|$1|K|3|L|5|6|7|10|8|@]|9|@]|C|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]]]

You can have a look at this: <a href="https://github.com/bmeck/session-web-sockets" rel="nofollow">https://github.com/bmeck/session-web-sockets</a>

or alternatively you can use: 

<pre><code>io.on('connection', function(client) { 
 var session = client.listener.server.viewHelpers; 
 // use session here 
});
</code></pre>

Hope this helps.

blocks|key|828276|text|这对于通过flashsocket传输的套接字不起作用(它不会向服务器发送所需的cookie)，但它可以可靠地用于其他任何事情。我只是在代码中禁用了flashsocket传输。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|828277|为了让它工作，在express/connect端，我显式地定义了会话存储，这样我就可以在socket中使用它：|828278|MemoryStore+=+require('connect/middleware/session/memory'),
var+session_store+=+new+MemoryStore();
app.configure(function+()+{
++app.use(express.session({+store:+session_store+}));
});|code-block|syntax|javascript|828279|然后，在我的套接字代码中，我包含了connect框架，这样我就可以使用它的cookie解析从cookie中检索connect.sid。然后我在会话存储中查找具有该connect.sid的会话，如下所示：|828280|var+connect+=+require('connect');
io.on('connection',+function(socket_client)+{
++var+cookie_string+=+socket_client.request.headers.cookie;
++var+parsed_cookies+=+connect.utils.parseCookie(cookie_string);
++var+connect_sid+=+parsed_cookies['connect.sid'];
++if+(connect_sid)+{
++++session_store.get(connect_sid,+function+(error,+session)+{
++++++//HOORAY+NOW+YOU'VE+GOT+THE+SESSION+OBJECT!!!!
++++});
++}
});|828281|然后，您可以根据需要使用该会话。|828282|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|U|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

This won't work for sockets going over the flashsocket transport (it doesn't send the server the needed cookies) but it reliably works for everything else. I just disable the flashsocket transport in my code.

To make it work, in the express/connect side, I explicitly define the session store so I can use it inside socket:

<pre><code>MemoryStore = require('connect/middleware/session/memory'),
var session_store = new MemoryStore();
app.configure(function () {
 app.use(express.session({ store: session_store }));
});
</code></pre>

Then inside my socket code, I include the connect framework so I can use its cookie parsing to retrieve the connect.sid from the cookies. I then look up the session in the session store that has that connect.sid like so:

<pre><code>var connect = require('connect');
io.on('connection', function(socket_client) {
 var cookie_string = socket_client.request.headers.cookie;
 var parsed_cookies = connect.utils.parseCookie(cookie_string);
 var connect_sid = parsed_cookies['connect.sid'];
 if (connect_sid) {
 session_store.get(connect_sid, function (error, session) {
 //HOORAY NOW YOU'VE GOT THE SESSION OBJECT!!!!
 });
 }
});
</code></pre>

You can then use the session as needed.

blocks|key|828338|text|看看这个：Socket.IO+Authentication|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|828339|我建议不要通过client.request...或client.listener...获取任何东西，因为它们不直接附加到client对象，并且总是指向最后登录的用户！|style|CODE|828340|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/4753957/socket-io-authentication/4782933#4782933^0|5|O|0|0|7|H|P|I|1O|6|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@$A|U|B|V|F|G]|$A|W|B|X|F|G]|$A|Y|B|Z|F|G]]|9|@]|C|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

See this: <a href="https://stackoverflow.com/questions/4753957/socket-io-authentication/4782933#4782933">Socket.IO Authentication</a>

I would suggest not fetching anything via <code>client.request...</code> or <code>client.listener...</code> as that is not directly attached to the <code>client</code> object and always point to the last logged in user!

blocks|key|828396|text|ID+sessions模块解决方案通过在客户端(脚本)级别公开会话ID将应用程序暴露给XSS攻击。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|828397|请改为检查此solution+(适用于Socket.IO+>=+v0.7)。请参见文档here。|offset|length|828398|entityMap|0|LINK|mutability|MUTABLE|url|http://www.danielbaulig.de/socket-ioexpress/|1|https://github.com/LearnBoost/socket.io/wiki/Authorizing^0|0|6|8|0|17|4|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]|$D|U|E|V|1|W]]|A|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]|N|$5|I|J|K|A|$L|O]]]]

The Socket.IO-sessions module solution exposes the app to XSS attacks by exposing the session ID at the client (scripting) level.

Check this <a href="http://www.danielbaulig.de/socket-ioexpress/">solution</a> instead (for Socket.IO >= v0.7). See docs <a href="https://github.com/LearnBoost/socket.io/wiki/Authorizing">here</a>.

blocks|key|828451|text|我不确定我做得对不对。https://github.com/LearnBoost/socket.io/wiki/Authorizing|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|828452|有了握手数据，您就可以访问cookie。在cookies中，您可以获取connect.sid，这是每个客户端的会话id。然后使用connect.sid从数据库中获取会话数据(我假设您使用的是RedisStore)|828453|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/LearnBoost/socket.io/wiki/Authorizing^0|B|1K|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

I am not sure that I am doing it right.
<a href="https://github.com/LearnBoost/socket.io/wiki/Authorizing" rel="nofollow">https://github.com/LearnBoost/socket.io/wiki/Authorizing</a>

With the handshake data, you can access to the cookies. And in the cookies, you can grab connect.sid which is the session id for each client. And then use the connect.sid to get the session data from database (I am assuming you are using RedisStore)

blocks|key|828509|text|我建议不要完全重复发明轮子。你需要的工具已经是一个npm包了，我想这就是你需要的：session.socket.io，我最近正在用它，我想它会很有帮助！！将express-session链接到socket.io层将会有很多好处！|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|828510|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/wcamarao/session.socket.io^0|15|H|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I suggest not to entirely reinvent the wheel. The tools you need is already an npm package.I think this is what you need: <a href="https://github.com/wcamarao/session.socket.io">session.socket.io</a>
I am using it in these days and it will be very helpful I guess!! Linking the express-session to the socket.io layer will have so many advantages!

blocks|key|828532|text|您可以使用express-socket.io-session。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|828533|与socket.io共享基于cookie的快速会话中间件。适用于express+>+4.0.0和socket.io+>+1.0.0，不会向后兼容。|828534|对我有效！！|828535|entityMap|0|LINK|mutability|MUTABLE|url|https://www.npmjs.com/package/express-socket.io-session^0|5|P|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

You can make use of <a href="https://www.npmjs.com/package/express-socket.io-session" rel="nofollow noreferrer">express-socket.io-session</a> . 

Share a cookie-based express-session middleware with socket.io. Works with express > 4.0.0 and socket.io > 1.0.0 and won't be backward compatible. 

Worked for me!!

blocks|key|1043499|text|自2022年2月起，Socket.IO+v4将支持此功能：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1043500|https://socket.io/docs/v4/faq/#usage-with-express-session|offset|length|1043501|const+express+=+require('express');
const+session+=+require('express-session');
const+app+=+express();

const+server+=+require('http').createServer(app);
const+io+=+require('socket.io')(server);

const+sessionMiddleware+=+session({+secret:+'keyboard+cat',+cookie:+{+maxAge:+60000+}});
//+register+middleware+in+Express
app.use(sessionMiddleware);
//+register+middleware+in+Socket.IO
io.use((socket,+next)+=>+{
++sessionMiddleware(socket.request,+{},+next);
++//+sessionMiddleware(socket.request,+socket.request.res,+next);+will+not+work+with+websocket-only
++//+connections,+as+'socket.request.res'+will+be+undefined+in+that+case
});

io.on('connection',+(socket)+=>+{
++const+session+=+socket.request.session;
++session.connections%2B%2B;
++session.save();
});

const+port+=+process.env.PORT+%7C%7C+3000;
server.listen(port,+()+=>+console.log('server+listening+on+port+'+%2B+port));|code-block|syntax|javascript|1043502|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|1L|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|H|7|W|8|@]|9|@]|A|$I|J]]|$1|K|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|C]]]]

As of February 2022 this is supported by Socket.IO v4:
<a href="https://socket.io/docs/v4/faq/#usage-with-express-session" rel="nofollow noreferrer">https://socket.io/docs/v4/faq/#usage-with-express-session</a>
<pre><code>const express = require('express');
const session = require('express-session');
const app = express();

const server = require('http').createServer(app);
const io = require('socket.io')(server);

const sessionMiddleware = session({ secret: 'keyboard cat', cookie: { maxAge: 60000 }});
// register middleware in Express
app.use(sessionMiddleware);
// register middleware in Socket.IO
io.use((socket, next) =&gt; {
 sessionMiddleware(socket.request, {}, next);
 // sessionMiddleware(socket.request, socket.request.res, next); will not work with websocket-only
 // connections, as 'socket.request.res' will be undefined in that case
});

io.on('connection', (socket) =&gt; {
 const session = socket.request.session;
 session.connections++;
 session.save();
});

const port = process.env.PORT || 3000;
server.listen(port, () =&gt; console.log('server listening on port ' + port));
</code></pre>

I'm using express framework. I want to reach session data from socket.io. I tried express dynamicHelpers with client.listener.server.dynamicViewHelpers data, but i can't get session data. Is there a simple way to do this? Please see the code

<pre><code>app.listen(3000);

var io = require('socket.io');
var io = io.listen(app);

io.on('connection', function(client){
 // I want to use session data here
 client.on('message', function(message){
 // or here
 });
 client.on('disconnect', function(){
 // or here
 }); 
});
</code></pre>

socket.io and session?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我使用的是express框架。我想从socket.io获取会话数据。我尝试使用client.listener.server.dynamicViewHelpers数据表示dynamicHelpers，但无法获取会话数据。有没有简单的方法可以做到这一点？请参阅代码app.listen(3000);var io = requ...

问socket.io和session？
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问socket.io和session？EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问socket.io和session？
EN