问题描述
问题是，在生产中，webapp是通过HTTPS提供的，而signalR中心是通过经典HTTP（例如http://test.com/SignalRNotificationH）提供的，正如预期的那样，大多数现代浏览器都会发出混合内容警告，拒绝与signalR交谈。
我的问题是：
1）有没有办法避免代码混合内容警告？
2）构建支持HTTPS的自托管http服务器是否值得？如果是这样，浏览器是否会通过https://test.com/SignalRNotificationH与客户端通过一些自签名证书进行交谈？
Problem is, in production the webapp is delivered over HTTPS and the signalR hub is delivered over classic HTTP (e.g. http://test.com/SignalRNotificationH) and, as expected, most modern browser throw a mixed-content warning and refuse to talk to signalR.
My questions are:
1) Is there a way to avoid the mixed-content warning by code?
2) Would it be worth to build a self-hosted http server supporting HTTPS? And, if so, will the browser talk to a client on https://test.com/SignalRNotificationH with some self-signed certificate?
推荐答案
这篇关于SIgnalR没有运行Https的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！