What is your server setup?
What OS?
What version of IIS?
Do you have websockets enabled?
Are you behind a proxy that disables websockets?
Are you behind a load balancer that disables websockets?
This error ususally happens if ASP.NET doesn't think the current request is a websocket request. That can happen for any number of reasons mentioned. Are you behind any type of proxy?
There is something in your network stack that doesn't like websockets and isn't sending the right headers for IIS to believe that it is a websocket request. This can be the browser version, a reverse proxy anti virus software any network device between the
client and server.
pantonis
Member
328 Points
260 Posts
SignalR exception
Jan 14, 2013 01:07 PM|LINK
I keep getting this exception all the time.
Exception information:
Exception type: InvalidOperationException
Exception message: Not a web socket request
Request URL: http://www.mysite.com/signalr/connect?transport=webSockets&connectionId=76c42778-d90f-4409-a6da-855f9f9c9fe3&connectionData=[{"name":"testhub"}]&tid=6
Request path: /signalr/connect
Any idea?
Please mark this post as answer if it helped you solve your problem
davidfowl
Contributor
2699 Points
611 Posts
Microsoft
Re: SignalR exception
Jan 16, 2013 07:21 PM|LINK
Can you give more details?
What is your server setup?
What OS?
What version of IIS?
Do you have websockets enabled?
Are you behind a proxy that disables websockets?
Are you behind a load balancer that disables websockets?
Senior SDE, ASP.NET Team, Microsoft
pantonis
Member
328 Points
260 Posts
Re: SignalR exception
Jan 17, 2013 09:42 AM|LINK
Server setup: Windows Server 2012 running IIS 8.0. WebSockets are enabled. IIS is NATTED. We don’t have any configuration with load balancing.
Please mark this post as answer if it helped you solve your problem
davidfowl
Contributor
2699 Points
611 Posts
Microsoft
Re: SignalR exception
Jan 17, 2013 04:39 PM|LINK
This error ususally happens if ASP.NET doesn't think the current request is a websocket request. That can happen for any number of reasons mentioned. Are you behind any type of proxy?
Senior SDE, ASP.NET Team, Microsoft
pantonis
Member
328 Points
260 Posts
Re: SignalR exception
Jan 18, 2013 08:13 AM|LINK
I have two environments:
one has no NAT or Proxy servers
second has a NAT rule from the Firweall
This happens on both envs
Thanks
Please mark this post as answer if it helped you solve your problem
davidfowl
Contributor
2699 Points
611 Posts
Microsoft
Re: SignalR exception
Jan 18, 2013 08:16 AM|LINK
What browser was it? Can you tell from the request information?
Senior SDE, ASP.NET Team, Microsoft
pantonis
Member
328 Points
260 Posts
Re: SignalR exception
Jan 18, 2013 09:11 AM|LINK
Thats what I get from the Request.Browser
Browser:
Type = Unknown
Name = Unknown
Version = 0.0
Major Version = 0
Minor Version = 0
Platform = Unknown
Is Beta = False
Is Crawler = False
Is AOL = False
Is Win16 = False
Is Win32 = False
Supports Frames = False
Supports Tables = False
Supports Cookies = True
Supports VBScript = False
Supports JavaScript = 0.0
Supports Java Applets = False
Supports ActiveX Controls = False
Please mark this post as answer if it helped you solve your problem
davidfowl
Contributor
2699 Points
611 Posts
Microsoft
Re: SignalR exception
Jan 28, 2013 06:05 AM|LINK
There is something in your network stack that doesn't like websockets and isn't sending the right headers for IIS to believe that it is a websocket request. This can be the browser version, a reverse proxy anti virus software any network device between the client and server.
Senior SDE, ASP.NET Team, Microsoft
pantonis
Member
328 Points
260 Posts
Re: SignalR exception
Jan 28, 2013 06:56 AM|LINK
you mean in the client's browser. If this is the case it shouldn't be using long polling or one of the other connection methods?
Please mark this post as answer if it helped you solve your problem
davidfowl
Contributor
2699 Points
611 Posts
Microsoft
Re: SignalR exception
Jan 28, 2013 09:10 AM|LINK
Yes it could be a client's browser and yes it probably does fallback to other transports after failing to connect via websockets.
Senior SDE, ASP.NET Team, Microsoft