Skip to content

Fix mixed content issue for browser connection - #215

Open
helly0d wants to merge 1 commit into
leapmotion:masterfrom
helly0d:secure
Open

Fix mixed content issue for browser connection#215
helly0d wants to merge 1 commit into
leapmotion:masterfrom
helly0d:secure

Conversation

@helly0d

@helly0d helly0d commented Oct 17, 2015

Copy link
Copy Markdown

When leap motion is not active and the SDK is loaded on a https page, all the browsers will throw error regarding mixed content.

The issue was from the attempt to degrade from wss to ws if the connection to the web socket failed, but ws is insecure and is not allowed with https.

@RecursiveCptHook

RecursiveCptHook commented Dec 11, 2019

Copy link
Copy Markdown
Contributor

Bit of an old PR (thanks for submitting the change)... but would be cool if we could potentially get some tests around this for before/after and then can merge. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants