{"action":"created","issue":{"url":"https://api.github.com/repos/aspnet/SignalR/issues/2515","repository_url":"https://api.github.com/repos/aspnet/SignalR","labels_url":"https://api.github.com/repos/aspnet/SignalR/issues/2515/labels{/name}","comments_url":"https://api.github.com/repos/aspnet/SignalR/issues/2515/comments","events_url":"https://api.github.com/repos/aspnet/SignalR/issues/2515/events","html_url":"https://github.com/aspnet/SignalR/issues/2515","id":333875603,"node_id":"MDU6SXNzdWUzMzM4NzU2MDM=","number":2515,"title":"Error when using Azure Traffic Manager Unexpected response code: 302","user":{"login":"zulander1","id":12099546,"node_id":"MDQ6VXNlcjEyMDk5NTQ2","avatar_url":"https://avatars3.githubusercontent.com/u/12099546?v=4","gravatar_id":"","url":"https://api.github.com/users/zulander1","html_url":"https://github.com/zulander1","followers_url":"https://api.github.com/users/zulander1/followers","following_url":"https://api.github.com/users/zulander1/following{/other_user}","gists_url":"https://api.github.com/users/zulander1/gists{/gist_id}","starred_url":"https://api.github.com/users/zulander1/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zulander1/subscriptions","organizations_url":"https://api.github.com/users/zulander1/orgs","repos_url":"https://api.github.com/users/zulander1/repos","events_url":"https://api.github.com/users/zulander1/events{/privacy}","received_events_url":"https://api.github.com/users/zulander1/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2018-06-19T23:37:51Z","updated_at":"2018-06-20T02:02:42Z","closed_at":null,"author_association":"NONE","body":"Hello,\r\nI am having some error using signalr and Traffic Manager on Azure.\r\nI have two app service in 2 two different region in Azure, both have the CORS set to *, and the routing method to: weighted.\r\nWhen the application is redirected to the second server I get the error. We cannot upgrade to core 2.1, both app service have the same version, ASP core 2.0. \r\nOur current solution is to set the Traffic Manager to priority, which sends the request to the same server…\r\nAny idea how I can resolve the issue?\r\n\r\n--------------------\r\nsignalr-client-1.0.0-alpha2-final.min.js:1 WebSocket connection to 'wss://URL/notifications?id=29173457-e7e5-4bf0-af5d-e7c8b5fae9a9' failed: Error during WebSocket handshake: Unexpected response code: 302\r\nPromise @ signalr-client-1.0.0-alpha2-final.min.js:1\r\nconnect @ signalr-client-1.0.0-alpha2-final.min.js:1\r\n(anonymous) @ signalr-client-1.0.0-alpha2-final.min.js:1\r\ng @ signalr-client-1.0.0-alpha2-final.min.js:1\r\nsignalr-client-1.0.0-alpha2-final.min.js:1 Uncaught (in promise) undefined\r\nh @ signalr-client-1.0.0-alpha2-final.min.js:1\r\nPromise.then (async)\r\ni @ signalr-client-1.0.0-alpha2-final.min.js:1\r\n(anonymous) @ signalr-client-1.0.0-alpha2-final.min.js:1\r\nd @ signalr-client-1.0.0-alpha2-final.min.js:1\r\nstart @ signalr-client-1.0.0-alpha2-final.min.js:1\r\n(anonymous) @ test.min.js:1\r\n(anonymous) @ test.min.js:1\r\n\r\n\r\nhttps://stackoverflow.com/questions/50938317/error-when-using-azure-application-gateway-unexpected-response-code-302\r\n\r\n**#EDIT: I made a mistake it's not an application gateway but Traffic Manager**"},"comment":{"url":"https://api.github.com/repos/aspnet/SignalR/issues/comments/398600440","html_url":"https://github.com/aspnet/SignalR/issues/2515#issuecomment-398600440","issue_url":"https://api.github.com/repos/aspnet/SignalR/issues/2515","id":398600440,"node_id":"MDEyOklzc3VlQ29tbWVudDM5ODYwMDQ0MA==","user":{"login":"anurse","id":7574,"node_id":"MDQ6VXNlcjc1NzQ=","avatar_url":"https://avatars3.githubusercontent.com/u/7574?v=4","gravatar_id":"","url":"https://api.github.com/users/anurse","html_url":"https://github.com/anurse","followers_url":"https://api.github.com/users/anurse/followers","following_url":"https://api.github.com/users/anurse/following{/other_user}","gists_url":"https://api.github.com/users/anurse/gists{/gist_id}","starred_url":"https://api.github.com/users/anurse/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/anurse/subscriptions","organizations_url":"https://api.github.com/users/anurse/orgs","repos_url":"https://api.github.com/users/anurse/repos","events_url":"https://api.github.com/users/anurse/events{/privacy}","received_events_url":"https://api.github.com/users/anurse/received_events","type":"User","site_admin":false},"created_at":"2018-06-20T02:02:42Z","updated_at":"2018-06-20T02:02:42Z","author_association":"MEMBER","body":"I don't think Traffic Manager supports a similar Session Affinity feature so yes, you wouldn't be able to route your SignalR traffic through Traffic Manager. One option to consider is the [Azure SignalR Service](https://azure.microsoft.com/en-us/services/signalr-service/). When you use that service, the clients connect directly to the SignalR Service endpoints, so you don't have to worry about load balancing the long-running SignalR connections."}}
{"actor":{"display_login":"anurse"}}