Having recently started playing with signalR, I got the following error:
WebSocket connection to 'ws://localhost/../signalr/connect?transport=webSockets&clientProtocol=1.4&connectionToken=DJquvX4%2B7kH0EzXZcCYSRPL66R3ytyc204DflljN1%2BgkHqi6Y5llDAAeUZTDKkDFFBQm6rdJooh8ck7LcejXVFZvhxE0iUJVD%2BZadN%2Ff5s13rc%2FMZD4WxsMSlToyvYid&connectionData=%5B%7B%22name%22%3A%22myapp%22%7D%5D&tid=4' failed: Error during WebSocket handshake: Unexpected response code: 500
This was odd as it was working fine on another development machine I was using. After serious amounts of hunting around and mucking about, I got it working by adding the following to the web.config:
<system.web>
<httpRuntime targetFramework="4.5"/>
</system.web>
Interestingly, I found the answer in the Application Event Logs :)
It's also worth checking that the application target framework is also set to 4.5 in case there is a conflict there too.
SyntaxHighlighter
Friday, 13 January 2017
Subscribe to:
Post Comments (Atom)
Labels
.net
(7)
ajax
(1)
android
(7)
apache
(1)
asp.net
(3)
asus
(2)
blogger
(2)
blogspot
(3)
c#
(16)
compact framework
(2)
cron
(1)
css
(1)
data
(1)
data recovery
(2)
dns
(1)
eclipse
(1)
encryption
(1)
excel
(1)
font
(1)
ftp
(1)
gmail
(5)
google
(4)
gopro
(1)
html
(1)
iis
(3)
internet explorer IE
(1)
iphone
(1)
javascript
(3)
kinect
(1)
linux
(1)
macro
(1)
mail
(9)
mercurial
(1)
microsoft
(3)
microsoft office
(3)
monitoring
(1)
mootools
(1)
ms access
(1)
mssql
(13)
mysql
(2)
open source
(1)
openvpn
(1)
pear
(2)
permissions
(1)
php
(12)
plesk
(4)
proxy
(1)
qr codes
(1)
rant
(4)
reflection
(3)
regex
(1)
replication
(1)
reporting services
(5)
security
(2)
signalr
(1)
sql
(11)
sqlce
(1)
sqlexpress
(1)
ssis
(1)
ssl
(1)
stuff
(1)
svn
(2)
syntax
(1)
tablet
(2)
telnet
(3)
tools
(1)
twitter
(1)
unix
(3)
vb script
(3)
vb.net
(9)
vba
(1)
visual studio
(2)
vpc
(2)
vpn
(1)
windows
(4)
woff
(1)
xbox 360
(1)
Great... Worked this for me
ReplyDeleteThanks!!!
ReplyDeleteIt works! Thanks
ReplyDeleteIt works! Thanks
ReplyDeleteTwo years later and it works! Thank you.
ReplyDeleteIt works thanks!
ReplyDeleteThanks for help!
ReplyDeleteDude, it's really works perfectly. Thank you very much
ReplyDeleteStill works in 2021! Thank you very much!
ReplyDeleteThanks for find this issue.
ReplyDelete