-
回答 1 已采纳
How is it possible to close a websocket connection and pass it a message / code?
The docs only define func (ws *Conn) Close() error without any arguments
I would like to receive the event from JavaScript like this:
websocket.onclose = function(event) {
console.log(event);
};
I am using golang.org/x/net/websocket
-
回答 1 已采纳
I'm attempting to port a NodeJS script that establishes and maintains a Websocket connection to a third-party server to Go using the gorilla/websocket package. In the Node script, a pong is received following a ping, and the connection is kept alive indefinitely. In the Go script, ping/pong works but the connection is dropped by the server after about 30 seconds.
I suspect that the pings that are sent using the Go websocket package are malformed, but I can't pinpoint the cause of this. Comparing the captured, encrypted network traffic while running these programs shows no difference in the response length of the TCP requests and responses, so this may not be the issue. Any help would be greatly appreciated!
websocket.js
#!/usr/bin/env node
// npm install websocket@1.0.25 --save
const WebSocketClient = require('websocket').client;
const client = new WebSocketClient();
let lastPing = new Date().getTime();
client.on('connectFailed', function(error) {
console.log('Connect Error: ' + error.toString());
});
client.on('connect', function(connection) {
console.log('Connected to Server...');
connection.on('error', function(error) {
console.log("Connection Error: " + error.toString());
});
connection.on('close', function() {
console.log('Connection Closed');
});
connection.on('message', function(message) {
if (message.type === 'utf8') {
console.log(message.utf8Data);
}
});
connection.on('pong', function(){
console.log('[pingpong] response took', (new Date().getTime() - lastPing) + 'ms');
})
function send(message) {
if (connection.connected) {
connection.sendUTF(message);
}
}
// Send a ping every 10s
// to keep the connection live
setInterval(function(){
lastPing = new Date().getTime();
connection.ping();
}, 10000);
});
client.connect('wss://ws.radarrelay.com/0x/v0/ws');
websocket.go
package main
import (
"flag"
"log"
"os"
"os/signal"
"time"
"github.com/gorilla/websocket"
)
var addr = "wss://api.radarrelay.com/0x/v0/ws"
func main() {
flag.Parse()
log.SetFlags(0)
timeoutDuration := 2 * time.Minute
interrupt := make(chan os.Signal, 1)
signal.Notify(interrupt, os.Interrupt)
c, _, err := websocket.DefaultDialer.Dial(addr, nil)
if err != nil {
log.Fatal("dial:", err)
} else {
log.Println("Connected to server")
}
c.SetPongHandler(func(str string) error {
log.Println("pong received", str)
return nil
})
defer c.Close()
done := make(chan struct{})
go func() {
defer c.Close()
defer close(done)
for {
c.SetReadDeadline(time.Now().Add(timeoutDuration))
_, message, err := c.ReadMessage()
if err != nil {
log.Println("read:", err)
return
}
if len(message) >= 2 {
message = message[2:]
}
log.Printf("recv: %s", message)
}
}()
ticker := time.NewTicker(10 * time.Second)
defer ticker.Stop()
for {
select {
case _ = <-ticker.C:
err := c.WriteMessage(websocket.PingMessage, []byte{})
if err != nil {
log.Println("write:", err)
return
} else {
log.Println("ping sent")
}
case <-interrupt:
log.Println("interrupt")
// To cleanly close a connection, a client should send a close
// frame and wait for the server to close the connection.
err := c.WriteMessage(
websocket.CloseMessage,
websocket.FormatCloseMessage(websocket.CloseNormalClosure, ""))
if err != nil {
log.Println("write close:", err)
return
}
select {
case <-done:
case <-time.After(time.Second):
}
c.Close()
return
}
}
}
-
回答 1 已采纳
Use Ratchet/React.
If I have less than 1000 connections it works good, but when number of connection is growing up - websockets closing automatically after connection.
What is the reason?
cat /proc/sys/fs/file-nr
5696 0 815941
open files (-n) 16384
cat /proc/sys/fs/file-max
815941
-
回答 1 已采纳
Using gorilla/websocket I'm connecting to some websocket (wss) endpoint and listening messages (only reading, not writing - this is important). This endpoint is always forcing closing connections after 10 minutes. Handling connection closing and reconnect will probably cause some incoming messages lost. How to handle connection in this case?
My suggestion is to keep pool of connections (2 connections or more). When first connection is being closed we can start using another (already connected) connection and start preparing new connection (or just reconnect). What do you think? Any drawbacks? "Swap" connections means stop using one gorouting and switch to another? Any ideas?
Important to note:
Endpoint is just broadcasting messages to all connections. No personalized messages, no authentification, no session-specific state etc.
Just reading, no writing at all.
-
回答 1 已采纳
How I can implement this kind of scenario:
1.I have LoginHandler which receives some user data - email and signedXml:
func LoginHandler(c *gin.Context) {
var (
err error
data LoginPost
)
if err = c.BindJSON(&data); err != nil {
c.JSON(http.StatusBadRequest, gin.H{"status": "error"})
return
}
...
c.JSON(http.StatusOK, gin.H{"status": "ok"})
}
2.I need to send signedXml to another server via websocket
3.Save result (success or error)
4.Close connection
Every HTTP request will open connection, send 1 message, get 1 result and finally close socket. I was trying with channel, but no success. Is this possible to implement my case?
UPDATE
package main
import (
"log"
"net/url"
"github.com/gorilla/mux"
"github.com/gorilla/websocket"
"net/http"
)
func indexHandler(w http.ResponseWriter, r *http.Request) {
message := r.FormValue("message")
w.Write([]byte(message))
}
func postHandler(w http.ResponseWriter, r *http.Request) {
var (
message = r.FormValue("message")
u = url.URL{Scheme: "ws", Host: "echo.websocket.org", Path: "/"}
err error
out []byte
conn *websocket.Conn
)
log.Printf("message: %s
", message)
log.Printf("connecting to %s
", u.String())
conn, _, err = websocket.DefaultDialer.Dial(u.String(), nil)
if err != nil {
log.Fatal("dial:", err)
}
log.Println("write")
if err = conn.WriteMessage(websocket.TextMessage, []byte(message)); err != nil {
log.Fatal("write:", err)
}
log.Println("read")
if _, out, err = conn.ReadMessage(); err != nil {
log.Fatal("read:", err)
}
w.Write(out)
log.Println("close")
conn.Close()
}
func main() {
r := mux.NewRouter()
r.HandleFunc("/", indexHandler).Methods("GET")
r.HandleFunc("/post", postHandler).Methods("POST")
http.Handle("/", r)
http.ListenAndServe(":8080", nil)
}
-
回答 1 已采纳 搞定了，我的代码写的基本没有问题，毕竟都是按着教程一步一步来的，主要问题在于，我的开发环境和教程不一致，我是前后端分离，请求8080即请求的前端项目，当然会超时然后建立连接失败。我查看了一下前后端各自的端口：前端8080，后端63000，然后把
```
this.sock = new WebSocket("ws:localhost:8080/websocket");//建立连接
```
改成
```
this.sock = new WebSocket("ws:localhost:63000/websocket");//建立连接
```
就可以了，换成后端的端口号。
---
以下是原问题
---
照着网上的教程写的例子，整合到自己的项目中。前端用vue写的，js里几乎和教程一模一样，主要问题在于
```
this.sock = new WebSocket("ws:localhost:8080/websocket");//建立连接
```
---
**创建的websocket内的方法都是null，如图：**
---
**然后观察控制台内过了一段时间报错，提示：**
```
WebSocket connection to 'ws://localhost:8080/websocket' failed: Connection closed before receiving a handshake response
```
---
**控制台错误详情见图：**
---
**前端代码：**
```
webSocket() {
debugger;
// 建立socket连接
if ('WebSocket' in window) {//判断当前浏览器是否支持webSocket
// this.sock = new WebSocket("ws:localhost:8080/bootTest/websocket");//建立连接（带后端项目名）
this.sock = new WebSocket("ws:localhost:8080/websocket");//建立连接（不带后端项目名）
} else {
alert('你的浏览器暂不支持websocket :(');
}
var sock = this.sock;
console.log(sock);
sock.onopen = function (e) {//成功建立连接
console.log(e);
};
sock.onmessage = function (e) {//接收到消息
console.log(e)
$(".message").append(""+e.data+"")
};
sock.onerror = function (e) {//连接发生错误
console.log(e);
};
sock.onclose = function (e) {//连接关闭
console.log(e);
};
////监听窗口关闭事件，当窗口关闭时，主动去关闭websocket连接，防止连接还没断开就关闭窗口，server端会抛异常。
window.onbeforeunload = function(){
websocket.close();
};
}
```
---
---
---
---
后端代码：
```
import java.io.IOException;
import java.util.concurrent.CopyOnWriteArraySet;
import javax.websocket.server.PathParam;
import javax.websocket.server.ServerEndpoint;
import javax.websocket.*;
import lombok.extern.slf4j.Slf4j;
@Slf4j
@ServerEndpoint("/websocket")
public class WebSocketServer {
//静态变量，用来记录当前在线连接数。应该把它设计成线程安全的。
private static int onlineCount = 0;
//concurrent包的线程安全Set，用来存放每个客户端对应的MyWebSocket对象。
private static CopyOnWriteArraySet webSocketSet = new CopyOnWriteArraySet();
//与某个客户端的连接会话，需要通过它来给客户端发送数据
private Session session;
/**
* 连接建立成功调用的方法*/
@OnOpen
public void onOpen(Session session) {
this.session = session;
webSocketSet.add(this); //加入set中
addOnlineCount(); //在线数加1
log.info("有新连接加入！当前在线人数为" + getOnlineCount());
try {
sendMessage("连接成功");
} catch (IOException e) {
log.error("websocket IO异常");
}
}
// //连接打开时执行
// @OnOpen
// public void onOpen(@PathParam("user") String user, Session session) {
// currentUser = user;
// System.out.println("Connected ... " + session.getId());
// }
/**
* 连接关闭调用的方法
*/
@OnClose
public void onClose() {
webSocketSet.remove(this); //从set中删除
subOnlineCount(); //在线数减1
log.info("有一连接关闭！当前在线人数为" + getOnlineCount());
}
/**
* 收到客户端消息后调用的方法
* @param message 客户端发送过来的消息
*/
@OnMessage
public void onMessage(String message, Session session) {
log.info("来自客户端的消息:" + message);
//群发消息
for (WebSocketServer item : webSocketSet) {
try {
item.sendMessage(message);
} catch (IOException e) {
e.printStackTrace();
}
}
}
/**
* 发生错误
* @param session
* @param error
*/
@OnError
public void onError(Session session, Throwable error) {
log.error("发生错误");
error.printStackTrace();
}
public void sendMessage(String message) throws IOException {
this.session.getBasicRemote().sendText(message);
}
/**
* 群发自定义消息
* */
public static void sendInfo(String message) throws IOException {
log.info(message);
for (WebSocketServer item : webSocketSet) {
try {
item.sendMessage(message);
} catch (IOException e) {
continue;
}
}
}
public static synchronized int getOnlineCount() {
return onlineCount;
}
public static synchronized void addOnlineCount() {
WebSocketServer.onlineCount++;
}
public static synchronized void subOnlineCount() {
WebSocketServer.onlineCount--;
}
}
```
-
回答 1 已采纳
I'm pushing events from a redis subscription to a client who is connected via websocket. I'm having trouble unsubscribing and exiting the redis go routine when the client disconnects the websocket.
Inspired by this post, here's what I have thus far. I'm able to receive subscription events and send messages to the client via websocket, but when the client closes the websocket and the defer close(done) code fires, my case b, ok := <-done: doesn't fire. It seems to be overloaded by the default case???
package api
import (
...
"github.com/garyburd/redigo/redis"
"github.com/gorilla/websocket"
)
func wsHandler(w http.ResponseWriter, r *http.Request) {
var upgrader = websocket.Upgrader{
ReadBufferSize: 1024,
WriteBufferSize: 1024,
}
conn, err := upgrader.Upgrade(w, r, nil)
if err != nil {
HandleError(w, err)
return
}
defer conn.Close()
done := make(chan bool)
defer close(done)
for {
var req WSRequest
err := conn.ReadJSON(&req)
if err != nil {
HandleWSError(conn, err)
return
}
defer conn.Close()
go func(done chan bool, req *WSRequest, conn *websocket.Conn) {
rc := redisPool.Get()
defer rc.Close()
psc := redis.PubSubConn{Conn: rc}
if err := psc.PSubscribe(req.chanName); err != nil {
HandleWSError(conn, err)
return
}
defer psc.PUnsubscribe()
for {
select {
case b, ok := <-done:
if !ok || b == true {
return
}
default:
switch v := psc.Receive().(type) {
case redis.PMessage:
err := handler(conn, req, v)
if err != nil {
HandleWSError(conn, err)
}
case redis.Subscription:
log.Printf("%s: %s %d
", v.Channel, v.Kind, v.Count)
case error:
log.Printf("error in redis subscription; err:
%v
", v)
HandleWSError(conn, v)
default:
// do nothing...
log.Printf("unknown redis subscription event type; %s
", reflect.TypeOf(v))
}
}
}
}(done, &req, conn)
}
}
-
回答 4 已采纳 如题...
连接上了之后，过几分钟就会自动断开..
在多个浏览器测试过...结果都是这样...
-
回答 1 已采纳
I'm trying to create a client and a server using Go but for some reason the server reports the connection as "closed". As the code is trivial I can't think of anything wrong with my code. Any help is appreciated.
package main
import (
log "github.com/golang/glog"
"net/http"
"golang.org/x/net/websocket"
"time"
"flag"
)
type server struct {
payload chan string
}
// srv pushes the messages received via ws into srv.payload
func (srv *server) serve(ws *websocket.Conn) {
go func() {
var msg string
if err := websocket.Message.Receive(ws, &msg); err != nil {
log.Exit(err)
}
srv.payload <- msg
}()
return
}
// This example demonstrates a trivial client/ server.
func main() {
flag.Parse()
srv := server{payload: make(chan string, 10)}
http.Handle("/echo", websocket.Handler(srv.serve))
go func() {
err := http.ListenAndServe(":12345", nil)
if err != nil {
log.Errorf("ListenAndServe: " + err.Error())
}
}()
// give the server some time to start listening
time.Sleep(3 *time.Second)
//dial and test the response.
ws, err := websocket.Dial("ws://localhost:12345/echo", "", "http://localhost/?x=45")
if err != nil {
log.Exit(err)
}
ms := "test"
if err := websocket.Message.Send(ws, ms); err != nil {
log.Exit(err)
}
msg := <-srv.payload
if msg != ms{
log.Errorf("msg %v is not %v", ms)
}
}
Error
t.go:21] read tcp 127.0.0.1:12345->127.0.0.1:43135:
Edit:
After some try and error I've found that if I remove the go routine from the serve method it works but it doesn't make sense to me. Any idea why it doesn't work when websocket.Message.Receive is in a separate go routine?
package main
import (
log "github.com/golang/glog"
"net/http"
"golang.org/x/net/websocket"
"time"
"flag"
)
type server struct {
payload chan string
}
// srv pushes the messages received via ws into srv.payload
func (srv *server) serve(ws *websocket.Conn) {
var msg string
if err := websocket.Message.Receive(ws, &msg); err != nil {
log.Exit(err)
}
srv.payload <- msg
return
}
// This example demonstrates a trivial client/ server.
func main() {
flag.Parse()
srv := server{payload: make(chan string, 10)}
go func() {
http.Handle("/echo", websocket.Handler(srv.serve))
err := http.ListenAndServe(":12345", nil)
if err != nil {
log.Errorf("ListenAndServe: " + err.Error())
}
}()
// give the server some time to start listening
time.Sleep(3 *time.Second)
//dial and test the response.
ws, err := websocket.Dial("ws://localhost:12345/echo", "", "http://localhost/?x=45")
if err != nil {
log.Exit(err)
}
ms := "test"
if err := websocket.Message.Send(ws, ms); err != nil {
log.Exit(err)
}
msg := <-srv.payload
if msg != ms{
log.Errorf("msg %v is not %v", ms)
}
}
-
回答 1 已采纳
I have a WebSocket JSON-RPC server example that I want to use from a browser. When you access the URL "http:localhost:8080", the browser opens the WebSocket connection properly. But when the browser sends the WebSocket request, the server closes the WebSocket connection. I can't even see a trace of the RPC method being called on the server.
However, calling the server from a Go client works perfectly.
server.go
package main
import (
"log"
"net/http"
"net/rpc"
"net/rpc/jsonrpc"
"github.com/gorilla/websocket"
)
type Service struct{}
func (t *Service) Echo(req *string, res *string) error {
log.Printf("Service.Echo")
*res = *req
log.Printf("Service.Echo req:%s res:%s", *req, *res)
return nil
}
var upgrader = websocket.Upgrader{
ReadBufferSize: 1024,
WriteBufferSize: 1024,
}
func serveWS(w http.ResponseWriter, r *http.Request) {
ws, err := upgrader.Upgrade(w, r, nil)
defer ws.Close()
if err != nil {
log.Println(err)
return
}
jsonrpc.ServeConn(ws.UnderlyingConn())
}
func main() {
rpc.Register(new(Service))
http.Handle("/", http.FileServer(http.Dir("web")))
http.HandleFunc("/ws", serveWS)
http.ListenAndServe(":8080", nil)
}
web/index.html
<!DOCTYPE html>
<html lang="en">
<head>
<script type="text/javascript">
var ws = new WebSocket("ws://localhost:8080/ws");
ws.onopen = function(ev){
alert("open");
}
ws.onmessage = function(ev){
alert("message");
}
ws.onclose = function(ev){
alert("close");
}
function send() {
msg = {
method: "Service.Echo",
params: "hello",
id: 0
};
var s = JSON.stringify(msg);
alert(s);
ws.send(s);
}
</script>
</head>
<body>
<button onclick='send()'>Send</button>
</body>
</html>
client.go
package main
import (
"log"
"net/rpc/jsonrpc"
"github.com/gorilla/websocket"
)
func main() {
ws, _, err := websocket.DefaultDialer.Dial("ws://localhost:8080/ws", nil)
if err != nil {
log.Fatal("dial:", err)
}
defer ws.Close()
client := jsonrpc.NewClient(ws.UnderlyingConn())
req := "hello"
var res string
err = client.Call("Service.Echo", &req, &res)
if err != nil {
log.Fatal("Service.Echo error:", err)
}
log.Printf("Service.Echo: req:%s res:%s", req, res)
}
Do you know what the problem could be?
Thank you very much.
Cheers
-
is s的博客 WebSocket vue连接、客户端主动关闭实例 https://blog.csdn.net/WK313753744/article/details/56007028 https://blog.csdn.net/ll666634/article/details/79028930 用vue-cli搭建的项目 在common下新建个js文件内容... -
Rosie Lau的博客 ，我有以下的JavaScript客户端代码：var connection = new WebSocket('ws://localhost:8080/OmegaThings/registerdevice');connection.onopen = function() {console.log("Socket has been opened state = " + ... -
董玉环的博客 本篇文章帮大家学习Websocket关闭连接，包含了Websocket关闭连接使用方法、操作技巧、实例演示和注意事项，有一定的学习价值，大家可以用来参考。关闭连接标志着服务器和客户端之间的通信结束。使用onclose事件可以... -
weixin_34402408的博客 7.1.1.关闭WebSocket连接 为_关闭WebSocket连接_，端点需关闭底层TCP连接。端点应该使用一个方法完全地关闭TCP连接，以及TLS会话，如果合适，丢弃任何可能已经接收的尾随的字节。当必要时端点可以通过任何可用的... -
weixin_39820173的博客 WebSocket关于websocket的一个小demo，是聊天室，源代码地址：聊天室的github源代码websocket的背景现在，很多网站为了实现推送技术，所用的技术都是 Ajax 轮询或者long poll 。这种传统的模式带来很明显的缺点，即... -
weixin_39637571的博客 我们先看一下下面这张图：可以看到这是一个简易的聊天室，两个窗口的消息是实时发送与接收的，这个主要就是用我们今天要讲的websocket实现的。websocket是什么？ websocket是一种网络通信协议，我们都知道http协议，... -
乱搭巴士的博客 懒得修改了 直接附上满足我需求的代码： java文件 很多方法我没用到 package com.example.demo.websocket; ...import javax.websocket.*; import javax.websocket.server.ServerEndpoint; impor... -
仿佛轻云兮如敝月的博客 到目前为止,我发现在服务器上的@OnMessage注释上,当服务器通过调用session.close收到“退出”消息时,我正在关闭连接.然后在@OnMessage的末尾,我发出了强制返回,因为该方法需要返回,并且由于会话已经关闭,正是该返回... -
徐先生的猫的博客 WebSocket 协议是基于 TCP 的一种新的网络协议。它实现了浏览器与服务器全双工 (full-duplex) 通信—允许服务器主动发送信息给客户端。为什么需要WebSocket?大家都知道以前客户端想知道服务端的处理进度，要不停地... -
我偏不起名字的博客 背景最近项目新增了一个 websocket 服务，用 nginx 做了一个简单的端口转发，然后调用的时候发现报错：error: Unexpected server response: 426搜索引擎走一波，找到几篇相关文章：...解...