POST Object

Description

You can call this operation to add an object to a specified space by using an HTML form. This operation is an alternative of the PUT operation, allowing you to upload objects to user spaces by using a browser. Parameters are encoded and encapsulated into the message body as form fields and passed through POST. To call this operation, you must have the write permissions on the bucket.

Kingsoft Cloud Standard Storage Service (KS3) adds only complete objects. If you receive a success response, KS3 has added the entire object to the bucket.

KS3 is a distributed system. When KS3 receives multiple write requests for the same object, it writes the object in an overwrite way and keeps only the latest object. KS3 does not provide object locking when you write an object to the bucket. You can build this function into your application layer as required.

Request

Request syntax

POST / HTTP/1.1
Host: {BucketName}.{endpoint}
User-Agent: {browser_data}
Accept: {file_types}
Accept-Language: {Regions}
Accept-Charset: {character_set}
Keep-Alive: 300
Connection: keep-alive
Content-Type: multipart/form-data; boundary=9431149156168
Content-Length: {length}

--9431149156168
Content-Disposition: form-data; name="key"

{ObjectKey}
--9431149156168
Content-Disposition: form-data; name="KSSAccessKeyId"

{AccessKey}
--9431149156168
Content-Disposition: form-data; name="Policy"

{Policy}
--9431149156168
Content-Disposition: form-data; name="Signature"

{Signature}
--9431149156168
Content-Disposition: form-data; name="file"; filename="MyFilename.jpg"
Content-Type: image/jpeg

file_content
--9431149156168
Content-Disposition: form-data; name="submit"

Upload to KS3
--9431149156168--

Request parameters

No request parameter is used.

Request headers

This operation involves only common request headers. For more information, see Common request headers.

Form fields

The following entries are required in a KS3 encryption request.

The following entries are required for enabling default encryption.

The following headers are required for specifying a user-defined key for encryption.

Response

Response headers

This operation supports all common response headers. For more information, see Common response headers.

Operation-specific errors

This operation does not return operation-specific errors.

Usage notes

• You must have the write permissions on the bucket.
• The KSSAccessKeyId, policy, and signature fields are required unless an anonymous user has the write permissions on the bucket. For more information, see Post Policy
• When you call this operation, make sure that Content-Type is multipart/form-data.
• The policy specifies rules for uploading a form. The form must meet all the rules. The policy must contain all form entries other than KSSAccessKeyId, policy, signature, and file.
• You must have the ks3:PutObjectTagging permission to tag the object during the uploading. If you have the ks3:PutObject permission but not the ks3:PutObjectTagging permission, you can call this operation to upload an object without tags.
• You can add entries starting with x-kss-meta to add user-defined metadata. These entries must be defined in the policy.
• If KS3 returns a 403 error, check whether the form meets the policy.