PowerShell

Set a Multipart Part Body from a Stream

Demonstrates Rest.SetMultipartBodyStream, which uses a Stream as the body source for the selected multipart part.

The file paths are relative to the application's current working directory. Absolute paths may also be used. Supply the paths appropriate to your own environment.

Background. Streaming a part body is appropriate for large parts because the data is read incrementally from the source rather than being buffered entirely in memory. The part is otherwise assembled the same way — select the part, set its headers, then set its body.

Chilkat PowerShell Downloads

Download Chilkat for PowerShell

PowerShell

Add-Type -Path "C:\chilkat\ChilkatDotNet47-x64\ChilkatDotNet47.dll"

$success = $false

$rest = New-Object Chilkat.Rest
$bTls = $true
$bAutoReconnect = $true
$success = $rest.Connect("example.com",443,$bTls,$bAutoReconnect)
if ($success -eq $false) {
    $($rest.LastErrorText)
    exit
}

#  The file paths are relative to the application's current working directory.  Absolute paths
#  may also be used.  Supply the paths appropriate to your own environment.

#  Select the multipart part to build, and set its header fields.
$rest.PartSelector = "1"
$rest.AddHeader("Content-Disposition","form-data; name=`"field1`"")
$rest.AddHeader("Content-Type","application/octet-stream")

#  Use a Stream as the body source for the selected part.  The stream's source is a local file,
#  which is appropriate for large parts.
$partStream = New-Object Chilkat.Stream
$partStream.SourceFile = "qa_data/attachment.bin"
$success = $rest.SetMultipartBodyStream($partStream)
if ($success -eq $false) {
    $($rest.LastErrorText)
    exit
}

$responseText = $rest.FullRequestMultipart("POST","/api/upload")
if ($rest.LastMethodSuccess -eq $false) {
    $($rest.LastErrorText)
    exit
}

$($responseText)