Options
All
  • Public
  • Public/Protected
  • All
Menu

Interface CreateMultipartUploadRequest

example

Click here to see how to use CreateMultipartUploadRequest.

Hierarchy

Properties

bucketName

bucketName: string

The name of the bucket. Avoid entering confidential information. Example: my-new-bucket1

createMultipartUploadDetails

createMultipartUploadDetails: CreateMultipartUploadDetails

Request object for creating a multipart upload.

Optional ifMatch

ifMatch: undefined | string

The entity tag (ETag) to match with the ETag of an existing resource. If the specified ETag matches the ETag of the existing resource, GET and HEAD requests will return the resource and PUT and POST requests will upload the resource.

Optional ifNoneMatch

ifNoneMatch: undefined | string

The entity tag (ETag) to avoid matching. The only valid value is '*', which indicates that the request should fail if the resource already exists.

namespaceName

namespaceName: string

The Object Storage namespace used for the request.

Optional opcClientRequestId

opcClientRequestId: undefined | string

The client request ID for tracing.

Optional opcSseCustomerAlgorithm

opcSseCustomerAlgorithm: undefined | string

The optional header that specifies "AES256" as the encryption algorithm. For more information, see Using Your Own Keys for Server-Side Encryption.

Optional opcSseCustomerKey

opcSseCustomerKey: undefined | string

The optional header that specifies the base64-encoded 256-bit encryption key to use to encrypt or decrypt the data. For more information, see Using Your Own Keys for Server-Side Encryption.

Optional opcSseCustomerKeySha256

opcSseCustomerKeySha256: undefined | string

The optional header that specifies the base64-encoded SHA256 hash of the encryption key. This value is used to check the integrity of the encryption key. For more information, see Using Your Own Keys for Server-Side Encryption.

Optional retryConfiguration

retryConfiguration: RetryConfiguration

RetryConfiguration to be used for the request NOTE : Retries are not supported for requests that have binary or stream bodies this also affects UploadManager operations For all requests with binary/stream bodies, retry attempts are not made