You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 19, 2019. It is now read-only.
I am getting this error logged in SuperWebSocket err log file, when client connects to the server developed using SuperWebSocket. But it seems the upgrade request send by client during websocket handshake is fine.
I added some trace logs in SuperWebSocket and it seems GET and HTTP/1.1 is coming in two different lines during the ReadLine call on StringReader , resulting in ParseHandshake throwing exception.
But when same header is printed by Logger, upgrade request seems to be fine.
I am getting this error logged in SuperWebSocket err log file, when client connects to the server developed using SuperWebSocket. But it seems the upgrade request send by client during websocket handshake is fine.
I added some trace logs in SuperWebSocket and it seems GET and HTTP/1.1 is coming in two different lines during the ReadLine call on StringReader , resulting in ParseHandshake throwing exception.
But when same header is printed by Logger, upgrade request seems to be fine.
GET / HTTP/1.1
Pragma: no-cache
Cache-Control: no-cache
Host: accesscomeserver.qa.mymaxprocloud.com
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Key: RMK4qLOdY/JVzCP1CDbaJg==
Origin: http://accesscomeserver.qa.mymaxprocloud.com
Sec-WebSocket-Protocol: honeywell.isom.http
Sec-WebSocket-Extensions:
Sec-WebSocket-Version: 13
X-HON-ISOM-Authorization: Basic MDA0MDg0MjE2MzkwOjAwNDA4NDIxNjM5MA==
Authorization: Basic MDA0MDg0MjE2MzkwOmJDV040V2dPYkFTcXUydTI=
The text was updated successfully, but these errors were encountered: