0
votes

Here's the scenario I'm working on: We have an html5, javascript web client that is served by our website. This client communicates with our desktop application using websockets. It's the desktop application that acts as a websocket server. The server from which the web client is downloaded is secured with ssl. The problem is that if the client is downloaded with ssl, firefox forces all future websocket communications to be secured with ssl. The question is how can I an get a valid ssl certicate (self signed certificate won't do) for a server that runs on the localhost? Is there a way to workaround this constraint?

Thanks.

2
What is the latest on this issue? Trying to find a solve for it now that chrome by default blocks non ssl websockets...Jonesome Reinstate Monica

2 Answers

0
votes

I have finally purchased a certificate for one of our domains and included a SAN (subject alternative name) for localhost to the certificate. It works fine with Firefox now. The only downfall is that it'll work only until November 2015.

-1
votes

You can basically get a certificate from any CA. However, as one states "Use of certificates containing non-unique such as reserved IP addresses or internal server names represent a risk to your environment and others. The support for issuance of certificates containing such names will be discontinued no later than November 1st 2015."

ref: baseline requirements

internal server names