Chilkat HOME .NET Core C# Android™ AutoIt C C# C++ Chilkat2-Python CkPython Classic ASP DataFlex Delphi ActiveX Delphi DLL Go Java Lianja Mono C# Node.js Objective-C PHP ActiveX PHP Extension Perl PowerBuilder PowerShell PureBasic Ruby SQL Server Swift 2 Swift 3,4,5... Tcl Unicode C Unicode C++ VB.NET VBScript Visual Basic 6.0 Visual FoxPro Xojo Plugin
(Objective-C) Building a multipart/form-data Request for HTTP UploadUploading files to a web server typically requires building a multipart/form-data request where the files are contained in the sub-parts of the MIME request. Note: HTTP uploads require code on the server-side to receive the upload. For example, see Complete C# ASP.NET HTTP Upload Example This example produces the following HTTP multipart/form-data request: POST /something HTTP/1.1 Content-Type: multipart/form-data; boundary=------------070002080409050901090203 Host: domain Content-Length: 546 --------------070002080409050901090203 Content-Disposition: form-data; name="fileA"; filename="fileA.txt" Content-Type: text/plain This is the contents of file A --------------070002080409050901090203 Content-Disposition: form-data; name="fileB"; filename="fileB.txt" Content-Type: text/plain This is the contents of file B --------------070002080409050901090203 Content-Disposition: form-data; name="fileC"; filename="fileC.txt" Content-Type: text/plain This is the contents of file C --------------070002080409050901090203--
#import <CkoHttpRequest.h> #import <NSString.h> // This example demonstrates building a multipart/form-data request. CkoHttpRequest *req = [[CkoHttpRequest alloc] init]; // The ContentType, HttpVerb, and Path properties should // always be explicitly set. req.HttpVerb = @"POST"; req.Path = @"/something"; req.ContentType = @"multipart/form-data"; // The contents and name of each file to be uploaded is provided // by calling any of the following methods: // AddBytesForUpload // AddBytesForUpload2 // AddFileForUpload // AddFileForUpload2 // AddStringForUpload // AddStringForUpload2 // For this example, we'll provide the contents of the files to be uploaded // directly as in-memory strings. [req AddStringForUpload: @"fileA" filename: @"fileA.txt" strData: @"This is the contents of file A" charset: @"utf-8"]; [req AddStringForUpload: @"fileB" filename: @"fileB.txt" strData: @"This is the contents of file B" charset: @"utf-8"]; [req AddStringForUpload: @"fileC" filename: @"fileC.txt" strData: @"This is the contents of file C" charset: @"utf-8"]; // View the request that would be sent if SynchronousRequest was called: NSString *requestMime = [req GenerateRequestText]; NSLog(@"%@",requestMime); // A few important comments about the HTTP request that is generated: // // 1) Chilkat automatically generates a random boundary string. In 99.999% of cases, this should // be sufficient. // 2) The Content-Length header is automatically generated based on the actual length of the MIME message // that follows the intial (topmost) MIME header. // 3) The HOST header will automatically get filled in with the actual domain when SynchronousRequest // is called |
© 2000-2024 Chilkat Software, Inc. All Rights Reserved.