如何在Go中获取socket.io握手查询
已采纳
We use the go-socket.io package to run a socket server and we need to authenticate users with handshake query data.
In node.js we used code like:
authDataString = socket.handshake.query.authData;
and we need to do something similar in Go.
- 点赞
- 写回答
- 关注问题
- 收藏
- 复制链接分享
- 邀请回答
1条回答
相关推荐
- 回答 1 已采纳 We use the go-socket.io package to run a socket server and we need to authenticate users with handshake query data. In node.js we used code like: authDataString = socket.handshake.query.authData; and we need to do something similar in Go.
- 回答 3 已采纳 socket.io协作式文本工具，刚刷新不进行输入操作时，可以同步其他客户端输入的内容，一旦自己开始编辑，两个客户端之间的文本就不会发生变化了 客户端 " id="editor"> $('#editor').on('keyup',function(){ var para= $('#editor').val(); socket.emit('para',{paragraph:para}); }); socket.on('updated_para',function(data){ wenzi.innerHTML=data; }); 服务器端 socket.on('para',function(data){ console.log(data); socket.broadcast.emit('updated_para',data.paragraph); }); console.log（data）的话也能看见自己输入的文本，但是就是文本框内容不更新。
- 回答 3 已采纳 Situation We're using socket.io for mobile-server communications. Since we can't force-upgrade users' devices, if we want to upgrade to version 1 (non-back-compatible), we have to handle both versions on the server for a while. Question What are the options? My current favourite is to wrap both the old version and the new version in a multiplexer. It detects the version of the incoming request based on headers and query parameters and thereby knows which functions to invoke. Another (shittier) option is to wrap the new version in a module that can translate the old version of the protocol into the new version (and back again) when necessary. This suffers from a serious drawback. It would be time-consuming and uncertain work to ensure I've properly determined and handled all the tiny differences. Some differences might take some serious massaging. (In case you're curious or it's helpful to know, we're doing this in Go.)
- 回答 4 已采纳 I have a node.js server running on the port 8443. Whenever I try to run the application through the browser my socket.io keeps connecting for about 20 seconds before the url turns red at the end. Edit 3 : This is my directory structure and now with updated files /var/www/html/nodetest/ Inside this /node_modules /app.js /index.html Node JS is installed on server. Here is my main app.js code (as suggested in answer) : var app = require('express')(); var server = require('http').createServer(app); var io = require('socket.io')(server); var fs = require('fs'); // Run server to listen on port 8443. server = app.listen(8443, () => { console.log('listening on *:8443'); }); io.listen(server); io.sockets.on('connection', function(socket) { socket.emit('message', 'this is the message emitted by server'); }); app.get('/', function(req, res){ fs.readFile(__dirname + 'index.html', function(error, data) { res.writeHead(200); res.end(data); }); }); And this is my client browser side code: <html> <head> <script src="https://cdnjs.cloudflare.com/ajax/libs/socket.io/1.5.1 /socket.io.min.js"></script> <script type="text/javascript"> var websocket; function onload() { websocket = io.connect(); websocket.on('message',function(data) { console.log('Received a message from the server!',data); }); }; </script> </head> <body onload="onload()"> <div id="divId"></div> </body> </html> Here is an image of the error Now it shows 404 Error
- 回答 1 已采纳 如标题，接收到了tcp服务器的数据后，想转发给客户端。但是socket.io文档似乎没有这种方法。直接上代码。 服务器部分： **var express=require('express'); var app=express(); var fs =require('fs'); var net=require('net'); var http=require('http').createServer(app); var io=require('socket.io').listen(http); //nodeServer需要的变量 var nodeServer = new net.Socket(); var ExBuffer = require('./ExBuffer'); var len = 4027; var offset=4; var exBuffer = new ExBuffer().uint32Head().littleEndian(); var sbuf = new Buffer(4); //存储客户端的连接实例 var aSocket={}; app.use(express.static('public')); app.get('/',function(req,res){ res.sendfile(__dirname+'/index.html'); }); //连接到C服务器 nodeServer.connect(3102, '127.0.0.1', function() { console.log('CONNECTED TO: 127.0.0.1:3102' ); // 建立连接后立即向服务器发送数据，服务器将收到这些数据 nodeServer.write('your socket has connected'); }); var server = http.listen(8888, '127.0.0.1',function () { var host = server.address().address var port = server.address().port console.log("welcome to http://%s:%s", host, port) }); // 同客户端建立连接 io.sockets.on('connection', function (socketIO) { aSocket=socketIO; // 从客户端接收数据，然后发送至Tomcat socketIO.emit("test","your websocket has connected"); socketIO.on('fromWebClient', function (webClientData) { }); //客户端断开连接 socketIO.on('disconnect', function () { console.log('DISCONNECTED FROM CLIENT'); }); }); // 从C服务器接收数据 nodeServer.on('data', function (data) { if(data.readUInt8(0)==170){ sbuf.writeUInt32LE(len,0);//写入包长 exBuffer.put(sbuf); exBuffer.put(data); } else{ exBuffer.put(data); } console.log('nodeServer'+data.length); }); //当nodeServer收到完整的数据包时 exBuffer.on('data', function(buffer) { console.log('>> nodeServer receive data.length:'+buffer.length); //console.log(buffer); //console.log(buffer.readInt32LE(826)); var useData=byteArrayUntil.getUseJson(buffer,offset); console.log(aSocket); aSocket.emit['pushToWebClient',useData.hz]; }); // 为nodeServer添加“data”事件处理函数 // data是服务器发回的数据 // 为客户端添加“close”事件处理函数 nodeServer.on('close', function() { console.log('Connection closed'); }); //构造一个遍历函数,分别返回array或者json var byteArrayUntil=new function(){ this.getUseData=function(data,offset){ var arr=[]; for(var i=0;i var socket = io.connect(); socket.on("test", function (data) { console.log(data); }); socket.on('pushToWebClient', function (data) { console.log(data); }); 现在问题就是服务器的这一部分： exBuffer.on('data', function(buffer) { console.log('>> nodeServer receive data.length:'+buffer.length); //console.log(buffer); //console.log(buffer.readInt32LE(826)); var useData=byteArrayUntil.getUseJson(buffer,offset); console.log(aSocket); aSocket.emit['pushToWebClient',useData.hz]; }); 我把数据接收到了，最后一句转发给客户端不会。ps：不用管对应id问题，我只需要简单实现转发数据即可。 参考过这个文档（如果知道上面怎么处理可以不用继续看了）： var http = require('http'), 2 net = require('net'), 3 app = http.createServer().listen('8181'), 4 io = require('socket.io').listen(app), 5 nodeServer = new net.Socket(); 6 // 连接到Tomcat 7 nodeServer.connect(8007, '127.0.0.1', function() { 8 console.log('CONNECTED'); 9 }); 10 // 存储客户端的WebSocket连接实例 11 var aSocket = {}; 12 // 同客户端建立连接 13 io.sockets.on('connection', function (socketIO) { 14 // 从客户端接收数据，然后发送至Tomcat 15 socketIO.on('fromWebClient', function (webClientData) { 16 // 存储至映射表 17 aSocket[socketIO.id] = socketIO; 18 // 发送至Tomcat的数据中添加socket_id 19 webClientData['sid'] = socketIO.id; 20 // 发送String类型的数据至Tomcat 21 nodeServer.write(JSON.stringify(webClientData)); 22 }); 23 // 客户端断开连接 24 socketIO.on('disconnect', function () { 25 console.log('DISCONNECTED FROM CLIENT'); 26 }); 27 }); 28 29 // 从Tomcat接收数据 30 nodeServer.on('data', function (data) { 31 var jsonData = JSON.parse(data.toString()); 32 // 分发数据至客户端 33 for (var i in jsonData.list) { 34 aSocket[jsonData.list[i]['sid']].emit('pushToWebClient', jsonData.list[i].data); 35 } 36 }); 有这么一句 aSocket[jsonData.list[i]['sid']].emit('pushToWebClient', jsonData.list[i].data); 虽然它实现的是通过id来实现建立一一对应连接，但是它还是独立出来使用了（查了一些资料都是在一起用的）， 到底该怎么实现呢？ps：不用管对应id问题，我只需要简单实现转发数据即可。 求大神帮助。
- 回答 1 已采纳 So I want to develop a chat system based on nodejs and socket.io, I have made a prototype and it works, the only thing that is stuck in my mind is how to store the chat messages in the database. I guess is not a good idea to store a message when a user hits the enter button, because this is live chat you could have 1000 just from a user in 30-60 min. The question is WHEN to store the data in the database, because I don't think that storing right away when the user hits enter will work on the long term? The chat works on the same idea as facebook.
- 回答 1 已采纳 I'm currently working on a mobile app that includes chat. The API backend is built with Laravel, but for the chat we're going to use Socket.io. We're using an SSL certificate from Let's Encrypt I'm having trouble getting Socket.io working. It does seem to connect because on page load the 'New connection' message appears to show up in the console in the browser, but any messages I send don't seem to be received. I think the Nginx config is probably incorrect. Here's the chat script in its current minimal form: var io = require('socket.io')(9000); io.on('connection', function (socket) { io.emit('connected', {'msg': 'Someone has connected'}); socket.on('messsage', function (data) { io.emit('relaymessage', data); }); socket.on('disconnect', function () { io.emit('disconnected'); }); }); And the client-side implementation: <!DOCTYPE html> <html> <head> <title>Laravel</title> <link href="https://fonts.googleapis.com/css?family=Lato:100" rel="stylesheet" type="text/css"> <style> html, body { height: 100%; } body { margin: 0; padding: 0; width: 100%; display: table; font-weight: 100; font-family: 'Lato'; } .container { text-align: center; display: table-cell; vertical-align: middle; } .content { text-align: center; display: inline-block; } .title { font-size: 96px; } </style> </head> <body> <div class="container"> <div class="content"> <div class="title">Chat</div> <div id="output"></div> <form> <textarea id="message"></textarea> <button id="submit">Submit</button> </form> </div> </div> <script type="text/javascript" src="//code.jquery.com/jquery-2.2.3.min.js"></script>> <script type="text/javascript" src="/client.js"></script>> <script type="text/javascript"> var socket = io(window.location.href); var txt = document.getElementById('message'); var btn = document.getElementById('submit'); socket.on('connected', function (data) { console.log('New connection'); }); socket.on('relaymessage', function (data) { console.log(data); $('div#output').append('<p>' + data.content + '</p>'); }); socket.on('disconnected', function () { console.log('Disconnected'); }); $('button#submit').on('click', function (event) { event.preventDefault(); var content = $('textarea#message').val(); socket.emit('message', { content: content }); $('textarea#message').val(''); }); </script>> </body> </html> Here's my Nginx config: server { listen 80; server_name example.com; return 301 https://$host$request_uri; } server { listen 443 ssl; server_name example.com; ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/example.com.com/privkey.pem; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; ssl_protocols TLSv1 TLSv1.1 TLSv1.2; ssl_prefer_server_ciphers on; ssl_ciphers 'EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH'; client_max_body_size 50M; server_tokens off; add_header X-Frame-Options SAMEORIGIN; add_header X-Content-Type-Options nosniff; add_header X-XSS-Protection "1; mode=block"; root /var/www/public; index index.php index.html index.htm; location / { try_files $uri $uri/ /index.php?$query_string; gzip on; gzip_proxied any; gzip_types text/plain text/css application/javascript application/x-javascript text/xml application/xml application/xml-rss text/javascript text/js application/json; expires 1y; charset utf-8; } location ~ \.php$ { try_files $uri /index.php =404; fastcgi_split_path_info ^(.+\.php)(/.+)$; fastcgi_pass unix:/var/run/php/php7.0-fpm.sock; fastcgi_index index.php; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; include fastcgi_params; } location /socket.io/ { proxy_pass http://localhost:9000; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_set_header Host $host; } location ~ /.well-known { root /var/www/public; allow all; } } Any idea as to what's gone awry?
- 回答 1 已采纳 I have made a chat with SocketIO who is working well on local, but i'm trying to deploy it on my Apache server. I'm using Php + NodeJs, not only Node I had ERR_CONNECTION_REFUSED error but solved it by opening the good port, Listen 8000 in my ports.conf My server.js look like this var io = require('socket.io').listen(8000); // Socket IO usage My client.js is var socket = io.connect('http://[MY SERVER IP]:8000'); // Other client code I use localhost in local but I changed by my server ip. But I still have this error XMLHttpRequest cannot load http://[MY_SERVER_IP]:8000/socket.io/?EIO=3&transport=polling&t=1455101301883-60. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'MY DOMAIN' is therefore not allowed access. The response had HTTP status code 404. I really don't know what to do, this is the first I try to deploy a Nodejs + php app. I had read some Stackoverflow questions to try to fix it, but i really don't know how... I don't knwo if this is due to my Apache conf or I must change some NodeJS or SocketIO conf Thanks for your help.
- 回答 1 已采纳 I want to send data from Android to Golang with socket.io . I do that with Nodejs correctly But now , i want do with Go. I cant find simple example.how can i do that?
- 回答 2 已采纳 I have been reading about websockets and also about socket.io. I understand websockets are not support but enough browsers yet to be realistically used. socket.io has browser support but appears to need node.js. With my hosting solution I have some space on a shared server, very limited control over the server and have access to php but there is no node.js. I have read that people can get socket.io to work with PHP. Question: seeing I have very limited server access, not control over ports, command line etc is it realistic that I could get socket.io working with PHP or should I just stick with the AJAX calls (I'm currently using)? Note: I've developed a chat solution and it appears it would be much more light weight if it was running with a socket solution. Also - is there good security with Sockets.io? thx
- 闵明的博客 在 Go 中使用 Socket.IOWebsocketWebsocket是全双工的基于TCP层的通信协议，为浏览器及网站服务器提供处理流式推送消息的方式。它不同于HTTP协议，但仍依赖HTTP的Upgrade头部进行协议的转换。websocket 协议通信分为...
- 诶jax的博客 大家参与的项目里多少都会有web server与browser需要长连接互联的场景，当然我也是，之前没有进行太多方案的调研（比如深入理解通信...两周前遇到个场景，前端大佬提需求说能否支持socket.io，之前写的websocket的se...
- 赶路人儿的博客 在 WebSocket API 中，浏览器和服务器只需要要做一个握手的动作，然后，浏览器和服务器之间就形成了一条快速通道。两者之间就直接可以数据互相传送。 socket.IO是一个websocket库，包括了客户端的js和服务器端...
- 布瑞泽的童话的博客 前言自己于express框架的基础上，以node为服务端，基于socket.io，实现了一个建议的聊天室。 成功从服务端推送数据到客户端。 效果如下图： 将客户端的信息传递到服务端后，服务端主动推送给客户端。websocket...
- 空中的羽毛的博客 服务器信息传输// send to current request socket client socket.emit(‘message’, “this is a test”);// sending to all clients except sender socket.broadcast.emit(‘message’, “this is a test”);// ...
- 江南-一苇渡江的博客 其实，早就应该跟大家分享golang中关于websocket的使用，但是一直不知道从何入手，也不能够很清晰的描述出来。今天就浅尝辄止，通过第三方库实现websocket。WebSocketWebSocket协议是基于TCP的一种新的网络协议。它...
- 小萝同学的博客 Origin：字段可选，通常用来表示在浏览器中发起此Websocket连接所在的页面，类似于Referer。但是，与Referer不同的是，Origin只包含了协议和主机名称。 WebSocket优点？ WebSocket是一个持久化的协议，而...
- ScumVirus的博客 由于之后要做的网页视频直播项目要用到socket.io模块，所以特地花时间研究了下，参照网上的代码做了些改进，自己写了个聊天室代码。不得不承认后端事实推送能力有点厉害，这是以前我用php一直苦恼的事情。下面简单...
- 2年前weixin_30326745的博客 失败：连接在接收握手响应之前关闭 是前后端握手过程失败，为啥会握手失败呢？ 服务端解包失败，到时握手失败，服务端应该会有提示， Error decoding a packet. 查看文档发现 socket 和 websocket 是两种...
- yunchong_zhao的博客 在讲解socket.io 先说下html5中新增的 webscoket 协议。 websocket的原生使用 就不细说了 WebSocket 是 HTML5 开始提供的一种在单个 TCP 连接上进行全双工通讯的协议。 WebSocket 使得客户端和服务器之间的数据...