PowerShell
PowerShell
Receive Text up to a Matching Sequence
See more Socket/SSL/TLS Examples
Demonstrates Socket.ReceiveUntilMatch, which receives bytes until an exact byte sequence is found. The match string is encoded using StringCharset and compared byte-for-byte.
Background. The comparison is case-sensitive with no Unicode normalization. This is useful for reading a message that ends with an application-defined marker delimiting the end of a response.
Chilkat PowerShell Downloads
Add-Type -Path "C:\chilkat\ChilkatDotNet47-x64\ChilkatDotNet47.dll"
$success = $false
$socket = New-Object Chilkat.Socket
# Connect to the server using TLS. The 3rd argument enables the TLS handshake after the TCP
# connection succeeds; the 4th is the maximum time to wait, in milliseconds.
$bTls = $true
$maxWaitMs = 5000
$success = $socket.Connect("example.com",5000,$bTls,$maxWaitMs)
if ($success -eq $false) {
$($socket.LastErrorText)
exit
}
# StringCharset controls the character encoding used when sending and receiving text.
$socket.StringCharset = "utf-8"
# Send a request using a simple application-defined text protocol in which each message ends with a
# CRLF.
$command = "STATUS`r`n"
$success = $socket.SendString($command)
if ($success -eq $false) {
$($socket.LastErrorText)
exit
}
# Receive bytes until an exact byte sequence is found. The match string is encoded using
# StringCharset and compared byte-for-byte. Here the server marks the end of its response with an
# application-defined marker.
$response = $socket.ReceiveUntilMatch("<EOM>")
if ($socket.LastMethodSuccess -eq $false) {
$($socket.LastErrorText)
exit
}
$($response)