I have different customers with servers, and would like to know the behavior if a server admin doesn't set the "WebSocket Protocol" on their IIS web server...
I have not yet implemented SignalR on in our application, so I am not specifically seeing a problem. My application is installed on customers servers, of which I have no control, and I wouldn't want the whole application to be taken down if a server admin
doesn't have the WebSocket option on IIS. My hope would be SignalR is smart enough to not just check the IIS version, but also check if that specific component is installed and functional on the IIS server.
I have not yet implemented SignalR on in our application, so I am not specifically seeing a problem. My application is installed on customers servers, of which I have no control, and I wouldn't want the whole application to be taken down if a server admin
doesn't have the WebSocket option on IIS. My hope would be SignalR is smart enough to not just check the IIS version, but also check if that specific component is installed and functional on the IIS server.
When I'm new to a technology, library, feature, etc, I generally rely on the published specifications and documentation. Then I'll build a proof of concept and test to make sure the technology fits my needs.
I haven't been able to spot any specifications of the criteria SignalR uses to determine if the server is "able" to perform SignalR processing. Is it just if the server is IIS-8 or above? Are there other criteria? If you (or someone else) know of such
"specifications", I would love if you might be able to point me at them. Yes, I can can run a series of test to figure out the behavior, but my hope was that someone experience in using SignalR would be able to tell me their experience regarding the behavior
(or find it in a spec).
I haven't been able to spot any specifications of the criteria SignalR uses to determine if the server is "able" to perform SignalR processing. Is it just if the server is IIS-8 or above? Are there other criteria? If you (or someone else) know of such
"specifications", I would love if you might be able to point me at them. Yes, I can can run a series of test to figure out the behavior, but my hope was that someone experience in using SignalR would be able to tell me their experience regarding the behavior
(or find it in a spec).
I'm not sure why you are unable to find SignalR reference documentation. This stuff is openly published. Use a search engine or click the
Docs link above and drill into the technology your looking for.
This should get you started. Be sure to see the left navigation menu as there is a lot of information.
Thanks for sending me a link to the general specification. You're right, I'm easily able to find that...and I have spent time on google and looking through specifications, but looking through it, and haven't found any where it describes the question I posed.
If you're not experienced with using SignalR in this area, that's fine. I appreciate you giving me general info...but I was hoping someone with specific experience might be able share some knowledge. Please don't feel obligated to respond back if you don't
have knowledge that would help.
Thanks for sending me a link to the general specification. You're right, I'm easily able to find that...and I have spent time on google and looking through specifications, but looking through it, and haven't found any where it describes the question I posed.
If you're not experienced with using SignalR in this area, that's fine. I appreciate you giving me general info...but I was hoping someone with specific experience might be able share some knowledge. Please don't feel obligated to respond back if you don't
have knowledge that would help.
I'm a little confused... this information is in the very first link.
Transports
SignalR supports the following techniques for handling real-time communication (in order of graceful fallback):
I appreciate the help, but this seems like it might not be your area, I'd appreciate if someone with experience in the area could respond. As much as I generally appreciate responses, you do not need to respond if you cannot understand the question.
I will repeat the question one more time. This is specifically what I would love for someone (with running experience of using SignalR and setting up servers).
I haven't been able to spot any specifications of the criteria SignalR uses to determine if the server is "able" to perform SignalR processing. Is it just if the server is IIS-8 or above? Are there other criteria? If you (or someone else) know of
such "specifications", I would love if you might be able to point me at them. Yes, I can can run a series of test to figure out the behavior, but my hope was that someone experience in using SignalR would be able to tell me their experience regarding the
behavior (or find it in a spec).
None
0 Points
17 Posts
If IIS isn't configured for WebSocket Protocol, will SignalR client automatically drop down to lo...
Dec 17, 2019 04:11 PM|greenstone90|LINK
I have different customers with servers, and would like to know the behavior if a server admin doesn't set the "WebSocket Protocol" on their IIS web server...
(from https://www.beyondtrust.com/docs/remote-support/how-to/integrations/real-time-dashboard/microsoft-iis.htm) Under Web Server Role (IIS) > Role Services, expand the Application Development section and select WebSocket Protocol.
Will a browser client running the SignalR app still work, but automatically dropped down into "long polling" method of doing updates?
All-Star
44301 Points
19096 Posts
Re: If IIS isn't configured for WebSocket Protocol, will SignalR client automatically drop down t...
Dec 17, 2019 04:22 PM|mgebhard|LINK
That's what the docs state. Are you having a problem?
None
0 Points
17 Posts
Re: If IIS isn't configured for WebSocket Protocol, will SignalR client automatically drop down t...
Dec 17, 2019 04:44 PM|greenstone90|LINK
I have not yet implemented SignalR on in our application, so I am not specifically seeing a problem. My application is installed on customers servers, of which I have no control, and I wouldn't want the whole application to be taken down if a server admin doesn't have the WebSocket option on IIS. My hope would be SignalR is smart enough to not just check the IIS version, but also check if that specific component is installed and functional on the IIS server.
All-Star
44301 Points
19096 Posts
Re: If IIS isn't configured for WebSocket Protocol, will SignalR client automatically drop down t...
Dec 17, 2019 04:54 PM|mgebhard|LINK
When I'm new to a technology, library, feature, etc, I generally rely on the published specifications and documentation. Then I'll build a proof of concept and test to make sure the technology fits my needs.
None
0 Points
17 Posts
Re: If IIS isn't configured for WebSocket Protocol, will SignalR client automatically drop down t...
Dec 17, 2019 05:17 PM|greenstone90|LINK
I haven't been able to spot any specifications of the criteria SignalR uses to determine if the server is "able" to perform SignalR processing. Is it just if the server is IIS-8 or above? Are there other criteria? If you (or someone else) know of such "specifications", I would love if you might be able to point me at them. Yes, I can can run a series of test to figure out the behavior, but my hope was that someone experience in using SignalR would be able to tell me their experience regarding the behavior (or find it in a spec).
All-Star
44301 Points
19096 Posts
Re: If IIS isn't configured for WebSocket Protocol, will SignalR client automatically drop down t...
Dec 17, 2019 05:25 PM|mgebhard|LINK
I'm not sure why you are unable to find SignalR reference documentation. This stuff is openly published. Use a search engine or click the Docs link above and drill into the technology your looking for.
This should get you started. Be sure to see the left navigation menu as there is a lot of information.
https://docs.microsoft.com/en-us/aspnet/core/signalr/introduction?view=aspnetcore-3.1
https://docs.microsoft.com/en-us/aspnet/core/tutorials/signalr?view=aspnetcore-3.1&tabs=visual-studio
Plus the all the code is open source.
https://github.com/SignalR/SignalR
None
0 Points
17 Posts
Re: If IIS isn't configured for WebSocket Protocol, will SignalR client automatically drop down t...
Dec 17, 2019 07:10 PM|greenstone90|LINK
Thanks for sending me a link to the general specification. You're right, I'm easily able to find that...and I have spent time on google and looking through specifications, but looking through it, and haven't found any where it describes the question I posed.
If you're not experienced with using SignalR in this area, that's fine. I appreciate you giving me general info...but I was hoping someone with specific experience might be able share some knowledge. Please don't feel obligated to respond back if you don't have knowledge that would help.
All-Star
44301 Points
19096 Posts
Re: If IIS isn't configured for WebSocket Protocol, will SignalR client automatically drop down t...
Dec 17, 2019 07:29 PM|mgebhard|LINK
I'm a little confused... this information is in the very first link.
Transports
SignalR supports the following techniques for handling real-time communication (in order of graceful fallback):
SignalR automatically chooses the best transport method that is within the capabilities of the server and client.
Also from the first link you can easily find the Transport specifications.
https://github.com/aspnet/AspNetCore/blob/master/src/SignalR/docs/specs/TransportProtocols.md
Lastly, you have the source code. I'm not sure what else you're look for...
None
0 Points
17 Posts
Re: If IIS isn't configured for WebSocket Protocol, will SignalR client automatically drop down t...
Dec 17, 2019 07:33 PM|greenstone90|LINK
I appreciate the help, but this seems like it might not be your area, I'd appreciate if someone with experience in the area could respond. As much as I generally appreciate responses, you do not need to respond if you cannot understand the question.
I will repeat the question one more time. This is specifically what I would love for someone (with running experience of using SignalR and setting up servers).
I haven't been able to spot any specifications of the criteria SignalR uses to determine if the server is "able" to perform SignalR processing. Is it just if the server is IIS-8 or above? Are there other criteria? If you (or someone else) know of such "specifications", I would love if you might be able to point me at them. Yes, I can can run a series of test to figure out the behavior, but my hope was that someone experience in using SignalR would be able to tell me their experience regarding the behavior (or find it in a spec).
All-Star
40485 Points
6231 Posts
Microsoft
Re: If IIS isn't configured for WebSocket Protocol, will SignalR client automatically drop down t...
Dec 18, 2019 01:55 AM|Fei Han - MSFT|LINK
Hi greenstone90,
This article describes the supported platforms of ASP.NET SignalR, you can check it.
https://docs.microsoft.com/en-us/aspnet/signalr/overview/getting-started/supported-platforms
Besides, you can refer to the following document to know details of transport selection process.
https://docs.microsoft.com/en-us/aspnet/signalr/overview/getting-started/introduction-to-signalr#transport-selection-process
With Regards,
Fei Han
MSDN Community Support
Please remember to "Mark as Answer" the responses that resolved your issue.