Fix websocket auth

[p53]

Look at
louketo#682
louketo#651
louketo#667

[escoand]

May I ask for a bit more context how this is fixed or could be worked around? In the recent releases is nothing obvious, at least for me.

[p53]

@escoand
Hi,

louketo#651, it might be solved using cookies
louketo#667, compression used for standard HTTP and websockets are different things as after upgrade gatekeeper is not involved in manipulation of websocket stream, for enabling compression with websocket i would look at Sec-Websocket-Extensions: permessage-deflate header which would be sent by client at start of connection, altough i am not sure how well is this supported by browsers, as it seems there is quite sparse information about it
louketo#682 - that might be solvable with cookies/HTTP CONNECT but i would need to try and verify

[p53]

@vishalgoel1988 could you elaborate more on 651 issue, describe exactly your use case? As having token in query param is less safe due to that it will be stored in browser history, usually logged by default by http servers, also not recomended by rfc