I wrote a website that the.net, a page used to Websocket, live chat, that is deployed to the IIS running, as long as the two open this page, then the entire site is locked, open new page has been loaded, as long as the two open page is closed, the new page immediately brush out! Vs extraneous to the IIS process debugging, open the new page, the third program would not have to enter my code, which is stopped by the IIS request!
If remove the long connection part of the page, so no matter how many the page open, lock will not lead to the entire site!
In vs2013 debugging when there is no this situation!

CodePudding user response:

The server version of Windows has 10 inbound restrictions

CodePudding user response:

Don't know what is your so-called websocket concrete,

Websocket IIS itself does not go, it goes with one of the biggest differences long HTTP connection is that it doesn't pit IIS, nor the pit browser side HTTP concurrency, go it alone the TCP protocol to access the websocket server, websocket signaling also decimal times than traditional http-based signaling,

Your so-called "deployed to IIS runtime," I don't know what you deploy the web site, you should take a closer look at your code, and see if there are any logical design bug,

For example the use of open source the.net class library Fleck websocket, is its website https://github.com/statianzo/Fleck so a few lines of code, you use a console application to perform this few lines of code, and then can use hundreds of web client to test it, does not need the IIS,

So you are using IIS server program, I don't know whether you write too complicated, "dead" instead,

CodePudding user response:

You should check (debug) you HTTP communication, see if there are enormous, when websocket communication, your HTTP communication should be "fixed",

Before asp.net should be made to a "pseudo websocket", that is to say, it automatically using HTTP connection to simulate the websocket long, rather than a true websocket, don't know whether you use the outdated, pseudo websocket function of asp.net,

CodePudding user response:

Right now, with the Windows service way to distribute the websocket server, use the console way to test it, don't use asp.net, do not use the IIS,

So you can save a lot of things in the future, because the websocket server-side programming with asp.net web programming, don't have any relationship between MAO,

Websocket server design and development, should not have as asp.net platform development plan, asp.net should be used to load the front page, with HTTP download resources files to the browser, and should not carry the websocket server, if you've ever through asp.net SignalR tasted the early adopters, so it should now be completely stripped from asp.net,

Websocket service, the future is a large message service system, communication is pure custom business data, and asp.net website but do,

CodePudding user response:

refer to the second floor sp1234 response:

don't know what is your so-called websocket concrete,

Websocket IIS itself does not go, it goes with one of the biggest differences long HTTP connection is that it doesn't pit IIS, nor the pit browser side HTTP concurrency, go it alone the TCP protocol to access the websocket server, websocket signaling also decimal times than traditional http-based signaling,

Your so-called "deployed to IIS runtime," I don't know what you deploy the web site, you should take a closer look at your code, and see if there are any logical design bug,

For example the use of open source the.net class library Fleck websocket, is its website https://github.com/statianzo/Fleck so a few lines of code, you use a console application to perform this few lines of code, and then can use hundreds of web client to test it, does not need the IIS,

So you are using IIS server program, I don't know whether you write too complicated, "dead" instead,

I'll use the.net comes, the features of the Websocket in whether the request is in an httphandler Websocket, and then establish long connection
If (context. IsWebSocketRequest)
{
.

The context. AcceptWebSocketRequest (SKT. ProcessChat);

.

Public async Task ProcessChat (AspNetWebSocketContext context)
{

The point is, it's in the vs debugging time has no problem

CodePudding user response:

Now I'm on ali cloud server and a new bug, an error in the browser
EbSocket connection to 'ws://m1. Imilu. La/hd/groupsocket? GID=4 'failed: Error during the WebSocket handshake: Unexpected response code: 200

Cannot establish a connection

CodePudding user response:

See sp1234 reply, I got a pure only an HTML page, page ashx projects, is to avoid the above said is a problem with the code itself
Code completely paste from http://www.cnblogs.com/langu/archive/2013/12/22/3485676.html, no change

Found that is still the same, as long as in IIS, opened the first page, can establish a long connection, and then opens the second page, but can not establish connection, and then opens the third page (page) doesn't work... !

CodePudding user response:

Problem solved? I also met the same problem with you, Websocket deployment in iis, visit a few times more web lock,

CodePudding user response:

reference sp1234 reply: 3/f

you should check (debug) you HTTP communication, see if there are enormous, when websocket communication, your HTTP communication should be "fixed",

Before asp.net should be made to a "pseudo websocket", that is to say, it automatically using HTTP connection to simulate the websocket long, rather than a true websocket, don't know whether you use the outdated, pseudo websocket function of asp.net,

You are my see one of the most active users in CSDN,,,,

CodePudding user response:

Under the.net websockt need IIS8 above! IE the default number of connections around 8, other browsers is unrestricted, based on websocket cloud customer service has been launched, I do have a problem, can communicate!

CodePudding user response:

Floor pig problem solved? I also encountered this problem... The current build links page refresh a 5 or 6 times more... CPU usage is soared in iis can't open the page...

CodePudding user response:

references 9 f wq8438 response:

Quote: reference sp1234 reply: 3/f

You should check (debug) you HTTP communication, see if there are enormous, when websocket communication, your HTTP communication should be "fixed",

Before asp.net should be made to a "pseudo websocket", that is to say, it automatically using HTTP connection to simulate the websocket long, rather than a true websocket, don't know whether you use the outdated, pseudo websocket function of asp.net,

You are my see one of the most active users in CSDN,,,,

I saw the most silly b is all sorts of fancy answer,,

CodePudding user response:

Iis websocket do have a lot of problems in practical application basically no one...

And write what I haven't seen someone in the web page it did.

Can't write winservice at the very least you write an exe is also ok...

A lot of online libraries a few words with three events...

Or find a TCP service DLL under the websocket protocol is compatible with the... This kind of things a lot.

I think you start with the place to begin is more appropriate. Rather than what to study on iis websocket..

CodePudding user response:

refer to the 13th floor by_ love reply:

iis websocket do have a lot of problems in the practical application basically no one...

And write what I haven't seen someone in the web page it did.

Can't write winservice at the very least you write an exe is also ok...

A lot of online libraries a few words with three events...

Or find a TCP service DLL under the websocket protocol is compatible with the... This kind of things a lot.

I think you start with the place to begin is more appropriate. Rather than what to study on iis websocket..

nullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnull