> On 27 July 2013 02:18, Daniel Veditz <dved...@mozilla.com> wrote: >> Uniformity is indeed important. Are you implying that some other browser >> is NOT blocking mixed-content WebSockets? > > For completeness, we're just checking the whole range of browsers at the > moment.
OK, thanks to a helpful intern we have the full run-down: Browsers that block mixed-content WebSockets: * Firefox (v22 & v23 tested, on Win/OSX/Ubuntu) * Firefox mobile (v22 on Android) * IE 10 and 11-preview (Windows 7) * IE 10 on SurfaceRT Browsers that allow mixed-content WebSockets: * Chrome (vv28-30 tested, on Win/OSX/Ubuntu) * Safari (v5 & v6 tested on Win/OSX) * Opera (v15 & v16-next on Win/OSX) * Safari on iOS 6 * Chrome 28 on iOS 6 * Chrome (v18 as stock browser on Android 4.2 on an S4, and v28 installed from Play) * Opera mobile (v14, v12 "Classic" on Android) Browsers without WebSockets at all: * IE 8, 9 * Opera mini * Opera 12 Test details: open https://www.websocket.org/echo.html. Make a wss:// connection. Make a ws:// connection. So IE and Firefox are on one side, Opera and Chrome and Safari on the other. Hardly any mobile browser users are having mixed-content WebSockets blocked. Nicholas ----- Nicholas Wilson: nicho...@nicholaswilson.me.uk _______________________________________________ dev-security mailing list dev-security@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-security
