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

Perl 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

 

 

 

(Perl) S3 Complete a Multipart Upload

This operation completes a multipart upload by assembling previously uploaded parts.

Processing of a Complete Multipart Upload request could take several minutes to complete. After Amazon S3 begins processing the request, it sends an HTTP response header that specifies a 200 OK response. While processing is in progress, Amazon S3 periodically sends whitespace characters to keep the connection from timing out. Because a request could fail after the initial 200 OK response has been sent, it is important that you check the response body to determine whether the request succeeded.

This example sends a POST request to complete a multipart upload, which looks like this:

POST /ObjectName?uploadId=UploadId HTTP/1.1
Host: BucketName.s3.amazonaws.com
Date: Date
Content-Length: Size
Authorization: authorization string

<CompleteMultipartUpload>
  <Part>
    <PartNumber>PartNumber</PartNumber>
    <ETag>ETag</ETag>
  </Part>
  ...
</CompleteMultipartUpload>

Chilkat Perl Downloads

Perl Module for Windows, Linux, Alpine Linux,
MAC OS X, Solaris, FreeBSD, OpenBSD,
Raspberry Pi and other single board computers

use chilkat();

#  This example requires the Chilkat API to have been previously unlocked.
#  See Global Unlock Sample for sample code.

#  The 1st step in an S3 multipart upload is to initiate it,
#  as shown here: Initiate S3 Multipart Upload

#  The 2nd step is to upload the parts
#  as shown here: S3 Upload Parts

#  The 3rd and final step (this example) is to complete the multipart upload.

#  Other S3 Multipart Upload Examples:
#  Abort Multipart Upload
#  List Parts

#  When the multipart upload was initiated, an UploadId was provided in the XML response, and it
#  was saved to a file.  Steps 2 and 3 begin by loading the XML and getting
#  the Upload ID.

$xmlInit = chilkat::CkXml->new();
$success = $xmlInit->LoadXmlFile("s3_multipart_uploads/initiate.xml");
if ($success != 1) {
    print "Did not find the initiate.xml XML file." . "\r\n";
    exit;
}

$uploadId = $xmlInit->getChildContent("UploadId");
print "UploadId = " . $uploadId . "\r\n";

#  We'll also need the XML file that contains a record of the parts
#  with part numbers and ETags.  (This file was produced when parts were being uploaded.)
$xmlPartsList = chilkat::CkXml->new();
$success = $xmlPartsList->LoadXmlFile("s3_multipart_uploads/partsList.xml");
if ($success != 1) {
    print "Did not find the partsList.xml XML file." . "\r\n";
    exit;
}

$rest = chilkat::CkRest->new();

#  Connect to the Amazon AWS REST server.
$bTls = 1;
$port = 443;
$bAutoReconnect = 1;
$success = $rest->Connect("s3.amazonaws.com",$port,$bTls,$bAutoReconnect);

#  ----------------------------------------------------------------------------
#  Important: For buckets created in regions outside us-east-1,
#  there are three important changes that need to be made.
#  See Working with S3 Buckets in Non-us-east-1 Regions for the details.
#  ----------------------------------------------------------------------------

#  Provide AWS credentials for the REST call.
$authAws = chilkat::CkAuthAws->new();
$authAws->put_AccessKey("AWS_ACCESS_KEY");
$authAws->put_SecretKey("AWS_SECRET_KEY");
$authAws->put_ServiceName("s3");

$success = $rest->SetAuthAws($authAws);

#  Set the bucket name via the HOST header.
#  In this case, the bucket name is "chilkat100".
$rest->put_Host("chilkat100.s3.amazonaws.com");

#  The "uploadId=UploadId" must be added as a query parameter.  This allows it to be
#  incorporated into the AWS signature calculation, which is a requirement.
#  Therefore, we use AddQueryParam:
$rest->AddQueryParam("uploadId",$uploadId);

#  Our ObjectName in this case is "somethingBig.zip".
$responseXml = $rest->fullRequestString("POST","/somethingBig.zip",$xmlPartsList->getXml());
if ($rest->get_LastMethodSuccess() != 1) {
    print $rest->lastErrorText() . "\r\n";
    exit;
}

#  When successful, the S3 Storage service will respond with a 200 response code,
#  with an XML body.
if ($rest->get_ResponseStatusCode() != 200) {
    #  Examine the request/response to see what happened.
    print "response status code = " . $rest->get_ResponseStatusCode() . "\r\n";
    print "response status text = " . $rest->responseStatusText() . "\r\n";
    print "response header: " . $rest->responseHeader() . "\r\n";
    print "response body: " . $responseXml . "\r\n";
    print "---" . "\r\n";
    print "LastRequestStartLine: " . $rest->lastRequestStartLine() . "\r\n";
    print "LastRequestHeader: " . $rest->lastRequestHeader() . "\r\n";
}

#  Load the XML response into Chilkat XMl and emit via GetXml to see the XML in a pretty-printed (indented) readable format.
$xml = chilkat::CkXml->new();
$xml->LoadXml($responseXml);
print $xml->getXml() . "\r\n";
print "----" . "\r\n";

print "Multipart upload completed." . "\r\n";

 

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