jribble/Java-Websockify — pull request #2 by jocull (2012-06-08 10:46:24+00:00)
Title: Correction for strict locations (rejections on iOS / Safari)

I've found an issue where iOS and Safari will reject requests because their locations are not an exact match. It's easily fixed by ensuring that they match. I'm not sure if this is the best way to detect if `ws://` or `wss://` should be used, so I am open to suggestions beyond this.

You can see the error in the Safari console here: http://imgur.com/W6fgu

Netty controls what WebSocket draft spec will be used, but their code seems to gracefully (and correctly) handle Draft 76 - used by iOS and Safari. You may have to check that the version you are linked against supports Draft 76. I am just using the latest Netty for this right now (3.4.6 currently).