SIgnalR not running over Https

Question

4.00/5 (3 votes)

See more:

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?

Posted 13-Jan-14 20:41pm

Mukeshlky4u

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sampath Lokuge · Answer 1 · 2014-01-14T01:20:00

Solution 1

You can run SignalR on Https.SSL is a host concern, not really related to SignalR.

Please check below mentioned links for more info.

Hosting SignalR under SSL/https

SignalR and HTTPS

I hope this will help to you :)

Posted 14-Jan-14 1:20am

Sampath Lokuge