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

The C# .NET Advantage: Features, Benefits, and Use CasesMay 05, 2025 am 12:01 AM

The advantages of C#.NET include: 1) Language features, such as asynchronous programming simplifies development; 2) Performance and reliability, improving efficiency through JIT compilation and garbage collection mechanisms; 3) Cross-platform support, .NETCore expands application scenarios; 4) A wide range of practical applications, with outstanding performance from the Web to desktop and game development.

Is C# Always Associated with .NET? Exploring AlternativesMay 04, 2025 am 12:06 AM

C# is not always tied to .NET. 1) C# can run in the Mono runtime environment and is suitable for Linux and macOS. 2) In the Unity game engine, C# is used for scripting and does not rely on the .NET framework. 3) C# can also be used for embedded system development, such as .NETMicroFramework.

The .NET Ecosystem: C#'s Role and BeyondMay 03, 2025 am 12:04 AM

C# plays a core role in the .NET ecosystem and is the preferred language for developers. 1) C# provides efficient and easy-to-use programming methods, combining the advantages of C, C and Java. 2) Execute through .NET runtime (CLR) to ensure efficient cross-platform operation. 3) C# supports basic to advanced usage, such as LINQ and asynchronous programming. 4) Optimization and best practices include using StringBuilder and asynchronous programming to improve performance and maintainability.

C# as a .NET Language: The Foundation of the EcosystemMay 02, 2025 am 12:01 AM

C# is a programming language released by Microsoft in 2000, aiming to combine the power of C and the simplicity of Java. 1.C# is a type-safe, object-oriented programming language that supports encapsulation, inheritance and polymorphism. 2. The compilation process of C# converts the code into an intermediate language (IL), and then compiles it into machine code execution in the .NET runtime environment (CLR). 3. The basic usage of C# includes variable declarations, control flows and function definitions, while advanced usages cover asynchronous programming, LINQ and delegates, etc. 4. Common errors include type mismatch and null reference exceptions, which can be debugged through debugger, exception handling and logging. 5. Performance optimization suggestions include the use of LINQ, asynchronous programming, and improving code readability.

C# vs. .NET: Clarifying the Key Differences and SimilaritiesMay 01, 2025 am 12:12 AM

C# is a programming language, while .NET is a software framework. 1.C# is developed by Microsoft and is suitable for multi-platform development. 2..NET provides class libraries and runtime environments, and supports multilingual. The two work together to build modern applications.

Beyond the Hype: Assessing the Current Role of C# .NETApr 30, 2025 am 12:06 AM

C#.NET is a powerful development platform that combines the advantages of the C# language and .NET framework. 1) It is widely used in enterprise applications, web development, game development and mobile application development. 2) C# code is compiled into an intermediate language and is executed by the .NET runtime environment, supporting garbage collection, type safety and LINQ queries. 3) Examples of usage include basic console output and advanced LINQ queries. 4) Common errors such as empty references and type conversion errors can be solved through debuggers and logging. 5) Performance optimization suggestions include asynchronous programming and optimization of LINQ queries. 6) Despite the competition, C#.NET maintains its important position through continuous innovation.

The Future of C# .NET: Trends and OpportunitiesApr 29, 2025 am 12:02 AM

The future trends of C#.NET are mainly focused on three aspects: cloud computing, microservices, AI and machine learning integration, and cross-platform development. 1) Cloud computing and microservices: C#.NET optimizes cloud environment performance through the Azure platform and supports the construction of an efficient microservice architecture. 2) Integration of AI and machine learning: With the help of the ML.NET library, C# developers can embed machine learning models in their applications to promote the development of intelligent applications. 3) Cross-platform development: Through .NETCore and .NET5, C# applications can run on Windows, Linux and macOS, expanding the deployment scope.

C# .NET Development Today: Trends and Best PracticesApr 28, 2025 am 12:25 AM

The latest developments and best practices in C#.NET development include: 1. Asynchronous programming improves application responsiveness, and simplifies non-blocking code using async and await keywords; 2. LINQ provides powerful query functions, efficiently manipulating data through delayed execution and expression trees; 3. Performance optimization suggestions include using asynchronous programming, optimizing LINQ queries, rationally managing memory, improving code readability and maintenance, and writing unit tests.

See all articles

Hot AI Tools

Undresser.AI Undress

AI-powered app for creating realistic nude photos

AI Clothes Remover

Online AI tool for removing clothes from photos.

Undress AI Tool

Undress images for free

Clothoff.io

AI clothes remover

Video Face Swap

Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

How to fix KB5055523 fails to install in Windows 11?

3 weeks agoByDDD

How to fix KB5055518 fails to install in Windows 10?

3 weeks agoByDDD

Roblox: Dead Rails - How To Tame Wolves

4 weeks agoByDDD

Roblox: Grow A Garden - Complete Mutation Guide

2 weeks agoByDDD

Strength Levels for Every Enemy & Monster in R.E.P.O.

4 weeks agoBy尊渡假赌尊渡假赌尊渡假赌

Hot Tools

Notepad++7.3.1

Easy-to-use and free code editor

SublimeText3 Mac version

God-level code editing software (SublimeText3)

Dreamweaver Mac version

Visual web development tools

VSCode Windows 64-bit Download

A free and powerful IDE editor launched by Microsoft

SecLists

SecLists is the ultimate security tester's companion. It is a collection of various types of lists that are frequently used during security assessments, all in one place. SecLists helps make security testing more efficient and productive by conveniently providing all the lists a security tester might need. List types include usernames, passwords, URLs, fuzzing payloads, sensitive data patterns, web shells, and more. The tester can simply pull this repository onto a new test machine and he will have access to every type of list he needs.

Hot Topics

1657

1415

1309

1257

1229