Cachable app rejects socket

[amark]

An entirely cache loaded app will fail to validate the socket because no REQ refreshed the session (tryst). Temporary fixes:

1. Force a non-cachable load.
2. Use incognito mode if security is not a concern.

[amark]

Upon further thought, I realized maybe having the remoteIP validate with the incoming socket might be bad and turned off by default.
Why? Well what if you have a configuration setup where the client is told to websocket connect to a different machine or whatever? Then there is no way for that other machine to know the req IP unless it was manually sent.
Hmmm.

[amark]

Pretty sure I fixed this, however I won't close until I have tests (#4) to prove so.