(Mono C#) S3 Streaming Upload with Expect: 100-continue

Demonstrates how to do an S3 streaming upload that includes an "Expect: 100-continue" request header. The purpose of sending an "Expect: 100-continue" header is to cleanly handle the case when the request fails, for whatever reason. (Failure reasons can be anything, such as a permissions problem, invalid authentication, etc.)

If no "Expect: 100-continue" header is included, and the AWS server rejects the request immediately after receiving the header, then this is what happens: The server closes the connection immediately after processing the request header. This results in a half-closed connection. Meanwhile, the client continues with sending the file data in the body of the HTTP request. Eventually, because nothing is consuming the data on the server-side, the outgoing socket buffer on the client (i.e. local machine) fills up, and an error such as "WSAECONNABORTED An established connection was aborted by the software in your host machine." is returned.

When the "Expect: 100-continue" is inclued, the server sends a response immediately after receiving the request header. A 100 response status code indicates that all is OK and the client should continue with sending the request body (i.e. file data), after which the server will respond with a final response.

Chilkat .NET Downloads Chilkat .NET Assemblies Chilkat for .NET Core Chilkat for Mono

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

// This first part is optional.  AWS authentication requires
// the SHA-256 hash of the request body (i.e. the contents of the file
// to be uploaded).  We can choose to pre-calculate the SHA-256 in a streaming fashion
// and then provide it to the authenticator object.  This way, if the file is
// extremely large, it never needs to completely reside in memory.
Chilkat.Crypt2 crypt = new Chilkat.Crypt2();
crypt.EncodingMode = "hex";
crypt.HashAlgorithm = "sha-256";
string fileToUploadPath = "qa_data/xml/hamlet.xml";
string hashStr = crypt.HashFileENC(fileToUploadPath);

Chilkat.Rest rest = new Chilkat.Rest();

// Connect to the Amazon AWS REST server.
bool bTls = true;
int port = 443;
bool bAutoReconnect = true;
bool 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.
Chilkat.AuthAws authAws = new Chilkat.AuthAws();
authAws.AccessKey = "AWS_ACCESS_KEY";
authAws.SecretKey = "AWS_SECRET_KEY";
authAws.ServiceName = "s3";
// Provide the pre-computed SHA-256 here:
authAws.PrecomputedSha256 = hashStr;

success = rest.SetAuthAws(authAws);

// Add an Expect: 100-continue request header
rest.AddHeader("Expect","100-continue");

// Set the bucket name via the HOST header.
// In this case, the bucket name is "chilkat100".
rest.Host = "chilkat100.s3.amazonaws.com";

Chilkat.Stream fileStream = new Chilkat.Stream();
fileStream.SourceFile = fileToUploadPath;

// Upload to the S3 Storage service.
// If the application provided the SHA-256 hash of the file contents (as shown above)
// then file is streamed and never has to completely reside in memory.
// If the application did NOT provide the SHA-256, then Chilkat will (internally) 
// load the entire file into memory, calculate the SHA-256, and then upload.
string responseStr = rest.FullRequestStream("PUT","/hamlet.xml",fileStream);
if (rest.LastMethodSuccess != true) {
    Debug.WriteLine(rest.LastErrorText);
    return;
}

// When successful, the S3 Storage service will respond with a 200 response code,
// with an XML body.  
if (rest.ResponseStatusCode == 200) {
    Debug.WriteLine(responseStr);
    Debug.WriteLine("File uploaded.");
}
else {
    // Examine the request/response to see what happened.
    Debug.WriteLine("response status code = " + Convert.ToString(rest.ResponseStatusCode));
    Debug.WriteLine("response status text = " + rest.ResponseStatusText);
    Debug.WriteLine("response header: " + rest.ResponseHeader);
    Debug.WriteLine("response body: " + responseStr);
    Debug.WriteLine("---");
    Debug.WriteLine("LastRequestStartLine: " + rest.LastRequestStartLine);
    Debug.WriteLine("LastRequestHeader: " + rest.LastRequestHeader);
}