MultipartFormData

open class MultipartFormData

Constructs multipart/form-data for uploads within an HTTP or HTTPS body. There are currently two ways to encode multipart form data. The first way is to encode the data directly in memory. This is very efficient, but can lead to memory issues if the dataset is too large. The second way is designed for larger datasets and will write all the data to a single file on disk with all the proper boundary segmentation. The second approach MUST be used for larger datasets such as video content, otherwise your app may run out of memory when trying to encode the dataset.

For more information on multipart/form-data in general, please refer to the RFC-2388 and RFC-2045 specs as well and the w3 form documentation.

Properties

  • The Content-Type header value containing the boundary used to generate the multipart/form-data.

    Declaration

    Swift

    open var contentType: String
    Show on GitHub

  • The content length of all body parts used to generate the multipart/form-data not including the boundaries.

    Declaration

    Swift

    public var contentLength: UInt64
    Show on GitHub

  • The boundary used to separate the body parts in the encoded form data.

    Declaration

    Swift

    public let boundary: String
    Show on GitHub

Lifecycle

Body Parts

  • Creates a body part from the data and appends it to the multipart form data object.

    The body part data will be encoded using the following format:

    • Content-Disposition: form-data; name=#{name} (HTTP Header)
    • Encoded data

    • Multipart form boundary

    Declaration

    Swift

    public func append(_ data: Data, withName name: String)
    Show on GitHub

  • Creates a body part from the data and appends it to the multipart form data object.

    The body part data will be encoded using the following format:

    • Content-Disposition: form-data; name=#{name} (HTTP Header)
    • Content-Type: #{generated mimeType} (HTTP Header)
    • Encoded data

    • Multipart form boundary

    Declaration

    Swift

    public func append(_ data: Data, withName name: String, mimeType: String)
    Show on GitHub

  • Creates a body part from the data and appends it to the multipart form data object.

    The body part data will be encoded using the following format:

    • Content-Disposition: form-data; name=#{name}; filename=#{filename} (HTTP Header)
    • Content-Type: #{mimeType} (HTTP Header)
    • Encoded file data

    • Multipart form boundary

    Declaration

    Swift

    public func append(_ data: Data, withName name: String, fileName: String, mimeType: String)
    Show on GitHub

  • Creates a body part from the file and appends it to the multipart form data object.

    The body part data will be encoded using the following format:

    • Content-Disposition: form-data; name=#{name}; filename=#{generated filename} (HTTP Header)
    • Content-Type: #{generated mimeType} (HTTP Header)
    • Encoded file data
    • Multipart form boundary

    The filename in the Content-Disposition HTTP header is generated from the last path component of the fileURL. The Content-Type HTTP header MIME type is generated by mapping the fileURL extension to the system associated MIME type.

    Declaration

    Swift

    public func append(_ fileURL: URL, withName name: String)
    Show on GitHub

  • Creates a body part from the file and appends it to the multipart form data object.

    The body part data will be encoded using the following format:

    • Content-Disposition: form-data; name=#{name}; filename=#{filename} (HTTP Header)
    • Content-Type: #{mimeType} (HTTP Header)
    • Encoded file data

    • Multipart form boundary

    Declaration

    Swift

    public func append(_ fileURL: URL, withName name: String, fileName: String, mimeType: String)
    Show on GitHub

  • Creates a body part from the stream and appends it to the multipart form data object.

    The body part data will be encoded using the following format:

    • Content-Disposition: form-data; name=#{name}; filename=#{filename} (HTTP Header)
    • Content-Type: #{mimeType} (HTTP Header)
    • Encoded stream data

    • Multipart form boundary

    Declaration

    Swift

    public func append(
        _ stream: InputStream,
        withLength length: UInt64,
        name: String,
        fileName: String,
        mimeType: String)
    Show on GitHub

  • Creates a body part with the headers, stream and length and appends it to the multipart form data object.

    The body part data will be encoded using the following format:

    • HTTP headers
    • Encoded stream data

    • Multipart form boundary

    Declaration

    Swift

    public func append(_ stream: InputStream, withLength length: UInt64, headers: HTTPHeaders)
    Show on GitHub

Data Encoding

  • Encodes all the appended body parts into a single Data value.

    It is important to note that this method will load all the appended body parts into memory all at the same time. This method should only be used when the encoded data will have a small memory footprint. For large data cases, please use the writeEncodedDataToDisk(fileURL:completionHandler:) method.

    Throws

    An AFError if encoding encounters an error.

    Declaration

    Swift

    public func encode() throws -> Data
    Show on GitHub

  • Writes the appended body parts into the given file URL.

    This process is facilitated by reading and writing with input and output streams, respectively. Thus, this approach is very memory efficient and should be used for large body part data.

    Throws

    An AFError if encoding encounters an error.

    Declaration

    Swift

    public func writeEncodedData(to fileURL: URL) throws
    Show on GitHub