Web Socket: IIS WebSocket Protocol feature need to be enabled for Socket.io?
For one of my application, I have implemented Web socket using socket.io and hosted in IIS. Currently socket connection helping to provide two way connection between client (React) and server (node.js).
As I mentioned, I have hosted my application in IIS. I have few doubts regarding Turn Windows features on or off -> Internet Information services -> World wide Web Services -> Application Development Features -> WebSocket Protocol. I have tested my application without enabling this feature, its working fine, but I would like to confirm below stuffs.
Do I really need to enable WebSocket protocol feature to make websocket work in my application? If so, how now it is working fine without enabling (I haven't do performance and stress testing, I may face issue on this).
What if I not enabling this feature? in short what is the actual use of this feature?
It would be helpful if anyone answer the above questions. Thanks in advance.
WebSocket as part of the HTTP stack requires a bunch of things to be ready on Windows (across multiple components), so hope this answer helps a little.
- HTTP.sys, a driver deep down in Windows OS, is upgraded to support the necessary packet communication required by the protocol.
- The IIS WebSocket module, an IIS extension which many other Microsoft frameworks (like SignalR) depend on.
So WebSocket support is by default on in HTTP.sys, and you don't need the IIS module if your framework (socket.io) has no dependency there.
Note that the "Summary" section provides several useful links,
(and the same article also indicates that IIS WebSocket module has conflicts with socket.io. But I doubt this is still applicable.)
Also note that if you are hosting Node.js web apps via HttpPlatformHandler, however, IIS WebSocket module is mandatory. Without it, HttpPlatformHandler cannot forward WebSocket traffic to Node.js.
- Python3.5 send object over socket (Pygame cam image)
- Port number handling on a multi user Windows server
- Python Socket gives "[Errno 24] Too many open files"
- Making recvfrom() function non-blocking
- Netty: how do I reduce delay between consecutive messages from the server?
- Java selector.select() blocking thread?
- Can an application having two main methods running individually be considered a multi-process application?
- UDP socket (multicast) not receiving data (Ubuntu)
- Socket chunk/buffer size
- Similar alternative for GetComponent on godot
- Multi-client sockets in Java?
- Multicast works on WSL1, but not WSL2
- c TCP socket connection refused for localhost
- Listening a port in c# (not a TCP port)
- Why do i need to define a endpoint on a socket twice to start receiving data?
- How can I convert string to utf8 in Dart?
- Send message from Java to socket server written in TypeScript
- Python split HTTP request in multiple fix-sized tcp packets
- Redirect linux process stdout to multiple incoming tcp connections
- How much overhead does SSL impose?
- ether type for adding custom protocol on ethernet frame
- Socket Timeout will kill the Thread in Python
- Packing multiple writes into single TCP packet
- TCP socket communication between parent and child process blocks after a few seconds (a few hundred bytes)
- Why does sendto reverse my IP address when using network byte order?
- A non-blocking socket operation could not be completed immediately
- TCP Server: recv() with dynamically increasing buffer size
- Peer to Peer Networking - with shared public IP and DHCP
- Difference between UNIX domain STREAM and DATAGRAM sockets?
- Running server on a phone, using cellular connection