【发布时间】:2018-04-13 14:52:37
【问题描述】:
我正在开发一个使用以下堆栈的 SignalR Core Web 应用程序:
- ASP.NET Core 2.1 预览版 2 (2.1.0-preview2-final)
- SignalR Core 1.0 预览版 2 (1.0.0-preview2-final)
- Microsoft.AspNetCore.Cors (2.1.0-preview2-final)
- Microsoft.AspNetCore.WebSockets (2.1.0-preview2-final)
客户端正在使用 SignalR NPM 包 (@aspnet/signalr)。
应用配置如下:
public void ConfigureServices(IServiceCollection services)
{
services.AddCors(options =>
{
options.AddPolicy(
"CorsPolicy",
builder => builder
.AllowCredentials()
.AllowAnyOrigin()
.AllowAnyMethod()
.AllowAnyHeader());
});
services.AddSignalR();
}
public void Configure(IApplicationBuilder app)
{
app.UseCors("CorsPolicy");
app.UseDefaultFiles();
app.UseStaticFiles();
app.UseWebSockets();
app.UseSignalR(routes =>
{
routes.MapHub<ClientHub>("/hubs/notifications");
});
}
在http://localhost本地运行时,客户端使用WS协议进行连接。但是在 Azure App Service 中部署时,它会回退到 SSE。
浏览器日志显示:
WebSocket connection to 'wss://xxxxxx.azurewebsites.net/hubs/notifications?id=ZRniWKpMLMPIyLhS5RSyAg' failed: Error during WebSocket handshake: Unexpected response code: 503
Information: SSE connected to https://xxxxxx.azurewebsites.net/hubs/notifications?id=ig47oOdQzbasdgrlr0cHaw
negotiate 方法似乎恢复了对 Websockets 的支持:
{"connectionId":"ZRniWKpMLMPIyLhS5RSyAg",
"availableTransports":[
{"transport":"WebSockets","transferFormats":["Text","Binary"]},
{"transport":"ServerSentEvents","transferFormats":["Text"]},
{"transport":"LongPolling","transferFormats":["Text","Binary"]}]
}
我错过了什么吗?还是不支持 WSS?
【问题讨论】:
-
您是否在 Azure 应用服务实例上启用了 WS?
-
/facepalm 我没看到有这样的设置
标签: c# asp.net-core websocket azure-web-app-service asp.net-core-signalr