32

I've got a websocket implementation that I'm trying to make work across browsers.

At some point, we'll migrate to wss:// (i.e. encrypted websockets) but for now, it's all ws://. When we serve a page from https that redirects to a ws host, we see the following:

  1. Chrome is okay.
  2. Firefox is okay if the allowInsecureFromHttps setting is set to true.
  3. IE10 barfs.

I know that the correct path is to simply implement wss, but in the meantime, I'm wondering if there's any configuration I can apply to IE10, similar to firefox's allowInsecureFromHttps that will permit a ws:// link to be opened from an https:// page.

Thanks!

Baljeetsingh Sucharia
  • 1,990
  • 1
  • 19
  • 37
Kyle Fransham
  • 1,859
  • 1
  • 19
  • 22
  • 1
    Did you find an answer to this yet? I too am facing the same problem with IE 10. – dhruv chopra Oct 08 '13 at 13:19
  • No answer to this yet... – Kyle Fransham Oct 09 '13 at 12:02
  • Even i am searching for this but no answer yet.. – Sohan Nov 25 '13 at 10:03
  • Have you tried to enable "Mixed Content" in: `tools > options > security > internet zone > miscellaneous > display mixed content` ? – moka Feb 21 '14 at 11:25
  • If you haven't resolved this, you might want to check this post: http://stackoverflow.com/questions/15114279/websocket-on-ie10-giving-a-securityerror "It looks like IE throws a SecurityError if you're trying to open a websocket on a local (intranet) domain. To overcome this, you may disable IE's automatic algorithm for recognizing local sites. This can be done in Tools > Internet Options > Security > Local Intranet > Sites" – ChileAddict - Intel Apr 16 '14 at 19:46
  • have you tried to add the site to your trusted sites? – workabyte May 08 '14 at 21:53
  • did you try to disable mixed secure and insecurity content block? http://helpdesk.princeton.edu/kb/display.plx?ID=9727 Can you add an apache httpd proxy with a ssl certificate to add ssl support? – Paizo May 28 '14 at 19:39
  • 1
    2022 Update: I checked the MSHTML source and HTTPS->HTTP websocket is unconditionally forbidden. EdgeHTML (used in the old Edge) would allow HTTPS->WS (unsecure HTTP) for localhost/127.0.0.1 only. – EricLaw Oct 17 '22 at 13:33

2 Answers2

3

Sorry to say, but there is no such configuration for IE10. You need to implement wss for it.

Ansuraj Khadanga
  • 128
  • 6
  • 1
    It was my experience from using Internet Explorer with automated Selenium tests that IE had very poor support for the nuances of handling HTTPS. – Jonathan Benn Jun 17 '14 at 15:53
1

If you do not have a better way, you can guide the user to the chrome or firefox, but this is not the best approach. Try javascript if you can help.

Feng Ye
  • 48
  • 9