Chilkat HOME .NET Core C# Android™ AutoIt C C# C++ Chilkat2-Python CkPython Classic ASP DataFlex Delphi ActiveX Delphi DLL Go Java Lianja Mono C# Node.js Objective-C PHP ActiveX PHP Extension Perl PowerBuilder PowerShell PureBasic Ruby SQL Server Swift 2 Swift 3,4,5... Tcl Unicode C Unicode C++ VB.NET VBScript Visual Basic 6.0 Visual FoxPro Xojo Plugin
(Perl) WebSocket over TLSEstablishing a WebSocket connection over TLS is exactly the same as for TCP, except for a few arguments passed to the Connect method.
use chilkat(); # 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. # $rest = chilkat::CkRest->new(); # ------------------------------------------------------------------ # To use TLS, connect to the TLS port (typically 443) and tell the rest.Connect method # that it's a TLS connection. # ------------------------------------------------------------------ $bUseTls = 1; $success = $rest->Connect("someserver.com",443,$bUseTls,0); if ($success != 1) { print $rest->lastErrorText() . "\r\n"; exit; } $ws = chilkat::CkWebSocket->new(); # Tell the WebSocket to use this connection. $success = $ws->UseConnection($rest); if ($success != 1) { print $ws->lastErrorText() . "\r\n"; exit; } # Add the standard WebSocket open handshake headers that will be needed. # (This adds the required HTTP request headers to the rest object.) $ws->AddClientHeaders(); # Add any additional headers that might be desired. # Two common WebSocketSpecific headers are "Sec-WebSocket-Protocol" and "Origin". $rest->AddHeader("Sec-WebSocket-Protocol","x-something"); $rest->AddHeader("Origin","http://someserver.com"); # Do the open handshake. $responseBody = $rest->fullRequestNoBody("GET","/something"); if ($rest->get_LastMethodSuccess() != 1) { print $rest->lastErrorText() . "\r\n"; exit; } # 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..) $statusCode = $rest->get_ResponseStatusCode(); print "Response status code: " . $statusCode . "\r\n"; if ($statusCode != 101) { print $responseBody . "\r\n"; print "-- Failed because of unexpected response status code." . "\r\n"; exit; } # 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. $success = $ws->ValidateServerHandshake(); if ($success != 1) { print $ws->lastErrorText() . "\r\n"; exit; } print "WebSocket connection successful." . "\r\n"; # The application may now begin sending and receiving frames on the WebSocket connection. # (At this point, we're done with the rest object...) |
© 2000-2024 Chilkat Software, Inc. All Rights Reserved.