(Tcl) WebSocket over TLS

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

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.

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

set rest [new_CkRest]

# ------------------------------------------------------------------
# To use TLS, connect to the TLS port (typically 443) and tell the rest.Connect method
# that it's a TLS connection.
# ------------------------------------------------------------------
set bUseTls 1
set success [CkRest_Connect $rest "someserver.com" 443 $bUseTls 0]
if {$success != 1} then {
    puts [CkRest_lastErrorText $rest]
    delete_CkRest $rest
    exit
}

set ws [new_CkWebSocket]

# Tell the WebSocket to use this connection.
set success [CkWebSocket_UseConnection $ws $rest]
if {$success != 1} then {
    puts [CkWebSocket_lastErrorText $ws]
    delete_CkRest $rest
    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-something"
CkRest_AddHeader $rest "Origin" "http://someserver.com"

# Do the open handshake.
set responseBody [CkRest_fullRequestNoBody $rest "GET" "/something"]
if {[CkRest_get_LastMethodSuccess $rest] != 1} then {
    puts [CkRest_lastErrorText $rest]
    delete_CkRest $rest
    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 {$statusCode != 101} then {
    puts "$responseBody"
    puts "-- Failed because of unexpected response status code."
    delete_CkRest $rest
    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 {$success != 1} then {
    puts [CkWebSocket_lastErrorText $ws]
    delete_CkRest $rest
    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 object...)

delete_CkRest $rest
delete_CkWebSocket $ws