Solution to the problem that the WebSocket deployment server cannot connect to the external network-C#.Net Tutorial-php.cn

Home

Backend Development

C#.Net Tutorial

Solution to the problem that the WebSocket deployment server cannot connect to the external network

黄舟

Sep 26, 2017 am 10:40 AM

webwebsocketserver

The first thing I want to say is the problem I encountered:

WebSocket connection to 'ws://www. xxxx.com/xxx/xx' failed: Error during WebSocket handshake: Unexpected response code: 200 The website is bound to the server. It is feasible to access the webSocket service directly on the server, but when I access it from the external network, this error is my biggest enemy. I have encountered a few petty thieves before, which can be easily solved. Let’s not mention it anymore. Let’s face the boss directly. I spent two afternoons looking for a solution, but I didn’t find it. Various solutions, but directly Not many people describe this problem when using .NET, but there are a lot of friends who have faced this problem. This has nothing to do with browser issues. I have tested it with Firefox, Google, and IE, and the expected problems still occur. Development platform: .NET, use ASP.NET MVC to build the website , in which the WebSocket service is used to design a discussion platform within the website.

<code> ##　First, take a look at my web page code##：#<pre class='brush:php;toolbar:false;'><script type="text/javascript"> $(function () { var url = "ws://xxxx:xx"+"@Url.Action("RequestProcessCenter")"; var ws; function connect() { ws = new WebSocket(url); $("#TopicContent").append("正在连接\n"); ws.onopen = function () { $("#TopicContent").append("已经连接\n"); }; ws.onmessage = function (evt) { console.log(evt.data); $("#TopicContent").append(evt.data); }; ws.onclose = function () { $("#TopicContent").append("已经关闭\n"); }; ws.onerror = function (evt) { console.log(evt.data); $("#TopicContent").append(evt.data); }; }; $("#send").click(function () { console.log(1); console.log(ws.readyState); console.log(WebSocket.OPEN); if (ws.readyState == WebSocket.OPEN) { ws.send($("#content").val()); $(this).val(""); } else { $("#TextMessge").append("连接已经关闭"); } }); $("#open").click(function () { connect(); }); $("#close").click(function () { ws.close(); }); }); </script></pre>Backend code:

public void RequestProcessCenter()
        {            if (HttpContext.IsWebSocketRequest)
            {                var currUser = GetCurrUser();                
            this._UserName = currUser.LoginName;
                HttpContext.AcceptWebSocketRequest(ProcessTopic);
            }            else
            {
                HttpContext.Response.Write("请求失败哟");
            }
        }

I think the URL format required by webSocket should not be mismatched.

The error is displayed as shown in the figure:

Returns 200. Although the request is successful, the result is not what we want.

The request method is indeed websocket, but the error exists. Why is this? I searched a lot of information, but I didn't find anything that really solved this problem. Maybe there was something wrong with the way I looked for it, but I looked at the first three pages of Baidu and didn't find the solution I wanted. I took it upon myself to test it, and found it to be effective.

The website I deployed on the server uses the default port 80, and the access will be invalid. What if the webSocket does not need to be bound to the same port as the website?

After this test:

1. Local port 80 is bound to the domain name webSocket uses the domain name, port 80 is invalid

2. Local port 80 is bound to the domain name webSocket uses the 2017 port host address to use the server The ip address is valid

3. The local 2017 port is not bound to the domain name and webSocket uses port 80 to be invalid

4. The local 2017 port is not bound to the domain name and webSocket uses the 2017 port to be valid

Summary Port 80 may be restricted by the system

On the other hand: There is no test whether domain name binding will affect it

Successfully solved the problem that although the external network returns 200, the websocket service cannot be used.

In this case, it should be noted that two websites need to be added to the IIS server, one for normal port 80 web page access, and the other for separate WebSocket function. These two websites can use the same A procedural version, this is what I did, no good ideas, noob level guy.

This website introduces some knowledge about WebSocket, and websocket uses ports 80-433 by default. Maybe I am wondering whether the port bound to my website and the same port bound to websocket are the external network requests. As for the occasional mistake, this issue will not be investigated for a while. The temporary function has been achieved, but I feel that this solution is not very good. It can only be said that it meets the needs, but it cannot simplify the demand process.

Leave a guess. When I access it on the server, it is feasible. I use port 80. The websocket service can be used normally. That is because when it is initiated on the server, it is directly The access is to my local service, so the firewall will not block it. However, when I use the external network to access, the network access rules may block my request. I click on the connection to initiate a call to the WebSocket service, and the service port also uses port 80, causing the firewall to identify it. Something went wrong.

The above is the detailed content of Solution to the problem that the WebSocket deployment server cannot connect to the external network. For more information, please follow other related articles on the PHP Chinese website!

Statement

The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn

SpringBoot怎么整合WebSocket实现后端向前端发送消息May 11, 2023 pm 02:07 PM

一、什么是websocket接口使用websocket建立长连接，服务端和客户端可以互相通信，服务端只要有数据更新，就可以主动推给客户端。WebSocket使得客户端和服务器之间的数据交换变得更加简单，允许服务端主动向客户端推送数据。在WebSocketAPI中，浏览器和服务器只需要完成一次握手，两者之间就直接可以创建持久性的连接，并进行双向数据传输。在WebSocketAPI中，浏览器和服务器只需要做一个握手的动作，然后，浏览器和服务器之间就形成了一条快速通道。两者之间就直接可以数据互相传送。

在ThinkPHP6中使用Nginx反向代理WebsocketJun 20, 2023 pm 09:31 PM

在近几年的互联网应用中，Websocket已经成为了一种非常重要的通信协议。ThinkPHP6作为一款优秀的PHP开发框架，也提供了对Websocket的支持。不过，在使用Websocket时，我们通常会涉及到跨域、负载均衡等问题，因此，在这篇文章中，我们将介绍如何在ThinkPHP6中使用Nginx反向代理Websocket。首先，我们需要明确一下Webs

Python服务器编程：实现WebSocket服务端Jun 19, 2023 am 09:51 AM

近年来，WebSocket技术日渐流行，成为了浏览器与服务器之间进行实时通信的标准选择。在Python中，我们可以通过一些成熟的库来实现WebSocket服务端的开发。本文将在介绍WebSocket技术的基础上，探索如何利用Python开发WebSocket服务端。一、什么是WebSocketWebSocket是一种在单个TCP

SpringBoot怎么实现WebSocket即时通讯May 12, 2023 am 09:13 AM

1、引入依赖org.springframework.bootspring-boot-starter-websocketorg.projectlomboklombokcom.alibabafastjson1.2.32、WebSocketConfig开启WebSocketpackagecom.shucha.deveiface.web.config;/***@authortqf*@Description*@Version1.0*@since2022-04-1215:35*/importorg.spri

浏览器支持WebTransport？它能替代WebSockets？Feb 23, 2023 pm 03:36 PM

许多应用程序，如游戏和直播等场景，需要一种机制来尽可能快地发送消息，同时可以接受无序、不可靠的数据传输方式。本机应用程序虽然可以使用原始 UDP 套接字，但这些在 Web 上不可用，因为它们缺乏加密、拥塞控制、同意发送机制（以防止 DDoS 攻击）。

PHP+Socket系列之实现websocket聊天室Feb 02, 2023 pm 04:39 PM

本篇文章给大家带来了关于php+socket的相关知识，其中主要介绍了怎么使用php原生socket实现一个简易的web聊天室？感兴趣的朋友下面一起来看一下，希望对大家有帮助。

Spring Boot中使用WebSocket实现推送和通知功能Jun 23, 2023 am 11:47 AM

在现代Web应用程序开发中，WebSocket是实现即时通信和实时数据传输的常用技术。SpringBoot框架提供了集成WebSocket的支持，使得开发者可以非常方便地实现推送和通知功能。本文将介绍SpringBoot中如何使用WebSocket实现推送和通知功能，并演示一个简单的实时在线聊天室的实现。创建SpringBoot项目首先，我们需要创建一

SpringBoot中怎么使用WebSocket实现点对点消息May 16, 2023 pm 12:58 PM

一、添加依赖，配置使用SpringSecurity里的用户。org.springframework.bootspring-boot-starter-security我们现在需要配置用户信息和权限配置。@ConfigurationpublicclassWebSecurityConfigextendsWebSecurityConfigurerAdapter{//指定密码的加密方式@SuppressWarnings("deprecation")@BeanPasswordEncode

See all articles