Last post Dec 26, 2013 06:23 AM by Jadkjk
Dec 26, 2013 06:23 AM|Jadkjk|LINK
I have a web application which is implemented using mvc 4 , jquery mobile (.net framework 4.5) and hosted on IIS 8.0 with websockets enabled.
When I try to access the website using safari or chrome on my ipad with ios7, the pages that are using SignalR connect to the hub using websockets (no spinning loader is showing).
However when enabling windows authentication, I have first faced the following issue: the authentication popup keeps showing multiple times even though credentials are entered correctly. Apparently it’s a safari issue on ios7 which I resolved by removing
the “negotiate” provider for windows authentication and keeping NTLM.
When the above issue is solved, the page is loading correctly after authenticating however the spinning loader keeps showing which indicates that SignalR is connecting to the hub using a different protocol then websockets (longpolling, serversideevent etc).
If I try to replicate the issue using chrome on windows 8, using the development tool I found out that when the client tries to connect using websocket I get “Unexpected response 401 Unauthorized” and then it falls back to server side events.
What should be done in order to enable websockets on ios7 safari when using windows authentication?