(PowerShell) WebSocket Connect through HTTP Proxy

This example shows how to establish a WebSocket connection through an HTTP proxy server.

Chilkat .NET Downloads Chilkat .NET Assemblies

Add-Type -Path "C:\chilkat\ChilkatDotNet47-9.5.0-x64\ChilkatDotNet47.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 HTTP Proxy example.
# We first use the Chilkat Socket object to establish a connection to the WebSocket server through an HTTP proxy.
# Next, the Rest object uses the Socket object for its connection.
# Finally, the WebSocket object uses the Rest object for its connection.  
# 

$rest = New-Object Chilkat.Rest
$socket = New-Object Chilkat.Socket

# Set the HTTP proxy domain or IP address, and port.
$socket.HttpProxyHostname = "192.168.1.79"
$socket.HttpProxyPort = 808

# Provide authentication to the HTTP proxy, if needed.
$socket.HttpProxyUsername = "HTTP_PROXY_LOGIN"
$socket.HttpProxyPassword = "HTTP_PROXY_PASSWORD"
$socket.HttpProxyAuthMethod = "Basic"

# Indicate that HTTP requests (i.e. the WebSocket opening handshake) will be sent over the socket.
# This is important for how the HTTP proxy connection is established.
$socket.HttpProxyForHttp = $true

# Connect to the websocket server through the HTTP proxy.
$bTls = $false
$port = 80
$maxWaitMs = 5000
$success = $socket.Connect("some-websocket-server.com",$port,$bTls,$maxWaitMs)
if ($success -ne $true) {
    $("Connect Failure Error Code: " + $socket.ConnectFailReason)
    $($socket.LastErrorText)
    exit
}

# Tell the Rest object to use the connected socket.
$success = $rest.UseConnection($socket,$true)
if ($success -ne $true) {
    $($rest.LastErrorText)
    exit
}

$ws = New-Object Chilkat.WebSocket

# Tell the WebSocket to use this connection.
$success = $ws.UseConnection($rest)
if ($success -ne $true) {
    $($ws.LastErrorText)
    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-some-websocket-subprotocol")
$rest.AddHeader("Origin","http://some-websocket-server.com")

# Do the open handshake.
$responseBody = $rest.FullRequestNoBody("GET","/something")
if ($rest.LastMethodSuccess -ne $true) {
    $($rest.LastErrorText)
    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.ResponseStatusCode
$("Response status code: " + $statusCode)

if ($statusCode -ne 101) {
    $($responseBody)
    $("-- Failed because of unexpected response status code.")
    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 -ne $true) {
    $($ws.LastErrorText)
    exit
}

$("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...)

$("Success.")