Chilkat Examples

ChilkatHOMEAndroid™Classic ASPCC++C#Mono C#.NET Core C#C# UWP/WinRTDataFlexDelphi ActiveXDelphi DLLVisual FoxProJavaLianjaMFCObjective-CPerlPHP ActiveXPHP ExtensionPowerBuilderPowerShellPureBasicCkPythonChilkat2-PythonRubySQL ServerSwift 2Swift 3/4TclUnicode CUnicode C++Visual Basic 6.0VB.NETVB.NET UWP/WinRTVBScriptXojo PluginNode.jsExcelGo

Tcl Examples

Web API Categories

ASN.1
Amazon Glacier
Amazon S3
Amazon S3 (new)
Amazon SES
Amazon SNS
Amazon SQS
Async
Azure Cloud Storage
Azure Service Bus
Base64
Bounced Email
Box
CAdES
CSR
CSV
Certificates
Compression
DKIM / DomainKey
DSA
Diffie-Hellman
Digital Signatures
Dropbox
Dynamics CRM
ECC
Email Object
Encryption
FTP
FileAccess
Firebase
GMail REST API
Geolocation
Google APIs
Google Calendar
Google Cloud Storage
Google Drive
Google Photos
Google Sheets
Google Tasks
Gzip
HTML-to-XML/Text

HTTP
HTTP Misc
IMAP
JSON
JSON Web Encryption (JWE)
JSON Web Signatures (JWS)
JSON Web Token (JWT)
Java KeyStore (JKS)
MHT / HTML Email
MIME
Microsoft Graph
NTLM
OAuth1
OAuth2
OneDrive
OpenSSL
Outlook
PEM
PFX/P12
POP3
PRNG
REST
REST Misc
RSA Encryption
SCP
SFTP
SMTP
SSH
SSH Key
SSH Tunnel
SharePoint
Socket/SSL/TLS
Spider
Stream
Tar Archive
Upload
WebSocket
XAdES
XML
XML Digital Signatures
XMP
Zip
curl

 

 

 

(Tcl) WebSocket Connect through SOCKS Proxy

This example shows how to establish a WebSocket connection through a SOCKS proxy.

Chilkat Tcl Extension Downloads

Chilkat Tcl Extension Downloads

load ./chilkat.dll

#  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.
# 

set rest [new_CkRest]

set socket [new_CkSocket]

#  Set the SOCKS proxy domain or IP address, port, and SOCKS version number (4 or 5)
CkSocket_put_SocksHostname $socket "192.168.1.79"
CkSocket_put_HttpProxyPort $socket 1080
CkSocket_put_SocksVersion $socket 5

#  Provide authentication to the SOCKS proxy, if needed.
CkSocket_put_SocksUsername $socket "SOCKS_PROXY_LOGIN"
CkSocket_put_SocksPassword $socket "SOCKS_PROXY_PASSWORD"

#  Connect to the websocket server through the HTTP proxy.
set bTls 0
set port 80
set maxWaitMs 5000
set success [CkSocket_Connect $socket "some-websocket-server.com" $port $bTls $maxWaitMs]
if {[expr $success != 1]} then {
    puts "Connect Failure Error Code: [CkSocket_get_ConnectFailReason $socket]"
    puts [CkSocket_lastErrorText $socket]
    delete_CkRest $rest
    delete_CkSocket $socket
    exit
}

#  Tell the Rest object to use the connected socket.
set success [CkRest_UseConnection $rest $socket 1]
if {[expr $success != 1]} then {
    puts [CkRest_lastErrorText $rest]
    delete_CkRest $rest
    delete_CkSocket $socket
    exit
}

set ws [new_CkWebSocket]

#  Tell the WebSocket to use this connection.
set success [CkWebSocket_UseConnection $ws $rest]
if {[expr $success != 1]} then {
    puts [CkWebSocket_lastErrorText $ws]
    delete_CkRest $rest
    delete_CkSocket $socket
    delete_CkWebSocket $ws
    exit
}

#  Add the standard WebSocket open handshake headers that will be needed.
#  (This adds the required HTTP request headers to the rest object.)
CkWebSocket_AddClientHeaders $ws

#  Add any additional headers that might be desired.
#  Two common WebSocketSpecific headers are "Sec-WebSocket-Protocol" and "Origin".
CkRest_AddHeader $rest "Sec-WebSocket-Protocol" "x-some-websocket-subprotocol"
CkRest_AddHeader $rest "Origin" "http://some-websocket-server.com"

#  Do the open handshake.
set responseBody [CkRest_fullRequestNoBody $rest "GET" "/something"]
if {[expr [CkRest_get_LastMethodSuccess $rest] != 1]} then {
    puts [CkRest_lastErrorText $rest]
    delete_CkRest $rest
    delete_CkSocket $socket
    delete_CkWebSocket $ws
    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..)
set statusCode [CkRest_get_ResponseStatusCode $rest]
puts "Response status code: $statusCode"

if {[expr $statusCode != 101]} then {
    puts "$responseBody"
    puts "-- Failed because of unexpected response status code."
    delete_CkRest $rest
    delete_CkSocket $socket
    delete_CkWebSocket $ws
    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.
set success [CkWebSocket_ValidateServerHandshake $ws]
if {[expr $success != 1]} then {
    puts [CkWebSocket_lastErrorText $ws]
    delete_CkRest $rest
    delete_CkSocket $socket
    delete_CkWebSocket $ws
    exit
}

puts "WebSocket connection successful."

#  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...)

puts "Success."

delete_CkRest $rest
delete_CkSocket $socket
delete_CkWebSocket $ws

 

© 2000-2019 Chilkat Software, Inc. All Rights Reserved.