Cachable app rejects socket

Open amark opened this issue 13 years ago • 3 comments

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

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

Nov 20 '12 08:11 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.

Dec 12 '12 10:12 amark

Pretty sure I fixed this, however I won't close until I have tests (https://github.com/amark/coalesce/issues/4) to prove so.

Oct 04 '13 09:10 amark