Geek asks and answers

How to avoid a “mixed content warning” using signal R, in a cross-domain scenario?

I am trying to create a prototype for interacting with the ↔ windows browser using SignalR.

The goal is simple: I have a tray application running on every client that reads a smart card and generates a value that needs to be passed to the web application.

I created my own SignalR host in the tray application, and the webpage successfully linked to it.

The problem is that Webapp is delivered via HTTPS, and the signalR concentrator is delivered via classical HTTP (for example http://localhost:8080), and, as expected, most modern browsers throw a warning about mixed content and refuse to talk with signalR.

My questions:

1) Is there a way to avoid mixed content warnings?

2) Is it worth building your own HTTP server that supports HTTPS? And, if so, will the browser talk to the client https://localhost/using some self-signed certificate?

thank

+5
source share
1 answer

Here you ask two questions:

Avoiding mixed content warnings in IE It's simple: go to the Tools menu - Internet Options and select the Security tab. Make sure the Internet zone is selected, and then click the "User Level" button. Scroll down to display mixed content and set Enable.

, - . , -. . .

.

SSL , , . , , , " ". , .

( , . HTTP). , ; , - , localhost.

+1

More articles:


All Articles