AutoIt
AutoIt
WebSocket Connect through SOCKS Proxy
See more WebSocket Examples
This example shows how to establish a WebSocket connection through a SOCKS proxy.Chilkat AutoIt Downloads
Local $bSuccess = False
; This example requires the Chilkat API to have been previously unlocked.
; See Global Unlock Sample for sample code.
; --------------------------------------------------
; This example borrows the code from the REST using SOCKS Proxy example.
; We first use the Chilkat Socket object to establish a connection to the WebSocket server through a SOCKS proxy.
; Next, the Rest object uses the Socket object for its connection.
; Finally, the WebSocket object uses the Rest object for its connection.
;
$oRest = ObjCreate("Chilkat.Rest")
$oSocket = ObjCreate("Chilkat.Socket")
; Set the SOCKS proxy domain or IP address, port, and SOCKS version number (4 or 5)
$oSocket.SocksHostname = "192.168.1.79"
$oSocket.HttpProxyPort = 1080
$oSocket.SocksVersion = 5
; Provide authentication to the SOCKS proxy, if needed.
$oSocket.SocksUsername = "SOCKS_PROXY_LOGIN"
$oSocket.SocksPassword = "SOCKS_PROXY_PASSWORD"
; Connect to the websocket server through the HTTP proxy.
Local $bTls = False
Local $iPort = 80
Local $iMaxWaitMs = 5000
$bSuccess = $oSocket.Connect("some-websocket-server.com",$iPort,$bTls,$iMaxWaitMs)
If ($bSuccess <> True) Then
ConsoleWrite("Connect Failure Error Code: " & $oSocket.ConnectFailReason & @CRLF)
ConsoleWrite($oSocket.LastErrorText & @CRLF)
Exit
EndIf
; Tell the Rest object to use the connected socket.
$bSuccess = $oRest.UseConnection($oSocket,True)
If ($bSuccess <> True) Then
ConsoleWrite($oRest.LastErrorText & @CRLF)
Exit
EndIf
$oWs = ObjCreate("Chilkat.WebSocket")
; Tell the WebSocket to use this connection.
$bSuccess = $oWs.UseConnection($oRest)
If ($bSuccess <> True) Then
ConsoleWrite($oWs.LastErrorText & @CRLF)
Exit
EndIf
; Add the standard WebSocket open handshake headers that will be needed.
; (This adds the required HTTP request headers to the rest object.)
$oWs.AddClientHeaders()
; Add any additional headers that might be desired.
; Two common WebSocketSpecific headers are "Sec-WebSocket-Protocol" and "Origin".
$oRest.AddHeader("Sec-WebSocket-Protocol","x-some-websocket-subprotocol")
$oRest.AddHeader("Origin","http://some-websocket-server.com")
; Do the open handshake.
Local $sResponseBody = $oRest.FullRequestNoBody("GET","/something")
If ($oRest.LastMethodSuccess <> True) Then
ConsoleWrite($oRest.LastErrorText & @CRLF)
Exit
EndIf
; If successful, the HTTP response status code should be 101,
; and the response body will be empty. (If it failed, we'll have a look
; at the response body..)
Local $iStatusCode = $oRest.ResponseStatusCode
ConsoleWrite("Response status code: " & $iStatusCode & @CRLF)
If ($iStatusCode <> 101) Then
ConsoleWrite($sResponseBody & @CRLF)
ConsoleWrite("-- Failed because of unexpected response status code." & @CRLF)
Exit
EndIf
; We have the expected 101 response, so let's now validate the
; contents of the response, such as the value sent by the server in the
; Sec-WebSocket-Accept header.
$bSuccess = $oWs.ValidateServerHandshake()
If ($bSuccess <> True) Then
ConsoleWrite($oWs.LastErrorText & @CRLF)
Exit
EndIf
ConsoleWrite("WebSocket connection successful." & @CRLF)
; The application may now begin sending and receiving frames on the WebSocket connection.
; (At this point, we're done with the rest and socket objects...)
ConsoleWrite("Success." & @CRLF)