AutoIt

WebSocket over TLS

See more WebSocket Examples

Establishing a WebSocket connection over TLS is exactly the same as for TCP, except for a few arguments passed to the Connect method. AutoIt

Local $bSuccess = False

;  This example requires the Chilkat API to have been previously unlocked.
;  See Global Unlock Sample for sample code.

;  --------------------------------------------------
;  A WebSocket connection begins life as an HTTP GET request containing a few special header fields,
;  such as "Upgrade: websocket".   

;  Your application will use the Chilkat Rest class to send the initial HTTP GET.  This allows you
;  to use the full capability of the Chilkat Rest class to customize the GET for any particular situation.
;  For example:
;  
;    - If custom HTTP request header fields must be added.
;    - If authentication is required, such as OAuth2, OAuth1, Basic HTTP Auth, etc.
;    - If HTTPS, SSH Tunneling, Proxies (HTTP or SOCKS), or other advanced connection or TLS features are required.
;  

$oRest = ObjCreate("Chilkat.Rest")
;  ------------------------------------------------------------------
;  To use TLS, connect to the TLS port (typically 443) and tell the rest.Connect method
;  that it's a TLS connection.
;  ------------------------------------------------------------------
Local $bUseTls = True
$bSuccess = $oRest.Connect("someserver.com",443,$bUseTls,False)
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-something")
$oRest.AddHeader("Origin","http://someserver.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 object...)