{"action":"created","issue":{"url":"https://api.github.com/repos/SignalR/SignalR/issues/3502","repository_url":"https://api.github.com/repos/SignalR/SignalR","labels_url":"https://api.github.com/repos/SignalR/SignalR/issues/3502/labels{/name}","comments_url":"https://api.github.com/repos/SignalR/SignalR/issues/3502/comments","events_url":"https://api.github.com/repos/SignalR/SignalR/issues/3502/events","html_url":"https://github.com/SignalR/SignalR/issues/3502","id":88745716,"node_id":"MDU6SXNzdWU4ODc0NTcxNg==","number":3502,"title":"Connection started but client events not called with websockets","user":{"login":"sav931","id":898701,"node_id":"MDQ6VXNlcjg5ODcwMQ==","avatar_url":"https://avatars3.githubusercontent.com/u/898701?v=4","gravatar_id":"","url":"https://api.github.com/users/sav931","html_url":"https://github.com/sav931","followers_url":"https://api.github.com/users/sav931/followers","following_url":"https://api.github.com/users/sav931/following{/other_user}","gists_url":"https://api.github.com/users/sav931/gists{/gist_id}","starred_url":"https://api.github.com/users/sav931/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sav931/subscriptions","organizations_url":"https://api.github.com/users/sav931/orgs","repos_url":"https://api.github.com/users/sav931/repos","events_url":"https://api.github.com/users/sav931/events{/privacy}","received_events_url":"https://api.github.com/users/sav931/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2015-06-16T14:37:29Z","updated_at":"2018-09-20T22:03:54Z","closed_at":null,"author_association":"NONE","body":"Hi,\nI'm using windows server 2012 and activated websockets on it.\nWhen signalr use websockets,  the connection is successfully started but no event in client side are called, only if I force signalr to connect with long polling....\n\nAny suggestion ?\n"},"comment":{"url":"https://api.github.com/repos/SignalR/SignalR/issues/comments/423348951","html_url":"https://github.com/SignalR/SignalR/issues/3502#issuecomment-423348951","issue_url":"https://api.github.com/repos/SignalR/SignalR/issues/3502","id":423348951,"node_id":"MDEyOklzc3VlQ29tbWVudDQyMzM0ODk1MQ==","user":{"login":"aspnet-hello","id":34947467,"node_id":"MDQ6VXNlcjM0OTQ3NDY3","avatar_url":"https://avatars3.githubusercontent.com/u/34947467?v=4","gravatar_id":"","url":"https://api.github.com/users/aspnet-hello","html_url":"https://github.com/aspnet-hello","followers_url":"https://api.github.com/users/aspnet-hello/followers","following_url":"https://api.github.com/users/aspnet-hello/following{/other_user}","gists_url":"https://api.github.com/users/aspnet-hello/gists{/gist_id}","starred_url":"https://api.github.com/users/aspnet-hello/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/aspnet-hello/subscriptions","organizations_url":"https://api.github.com/users/aspnet-hello/orgs","repos_url":"https://api.github.com/users/aspnet-hello/repos","events_url":"https://api.github.com/users/aspnet-hello/events{/privacy}","received_events_url":"https://api.github.com/users/aspnet-hello/received_events","type":"User","site_admin":false},"created_at":"2018-09-20T22:03:54Z","updated_at":"2018-09-20T22:03:54Z","author_association":"NONE","body":"This issue has been closed as part of issue clean-up as described in https://blogs.msdn.microsoft.com/webdev/2018/09/17/the-future-of-asp-net-signalr/. If you're still encountering this problem, please feel free to re-open and comment to let us know! We're still interested in hearing from you, the backlog just got a little big and we had to do a bulk clean up to get back on top of things. Thanks for your continued feedback!\r\n"}}
{"actor":{"display_login":"aspnet-hello"}}