OPTIONS Object
Last updated: 2019-12-16 17:51:15
Contents：
Description
This API is used to implement a pre-request for cross-origin object access configuration. Before making a real cross-origin resource sharing (CORS) request, you can make an OPTIONS request carrying the specific source origin, HTTP method, and header information to COS for it to determine whether a real request can be made. If there is no CORS configuration, 403 Forbidden will be returned. You can enable CORS for a bucket using the PUT Bucket cors API.
Request
Sample Request
OPTIONS /<ObjectKey> HTTP/1.1
Host: <BucketName-APPID>.cos.<Region>.myqcloud.com
Date: GMT Date
Origin: Origin
Access-Control-Request-Method: HTTPMethod
Access-Control-Request-Headers: RequestHeader
Authorization: Auth StringAuthorization: Auth String (see Request Signature for more information).
Request Headers
Common Headers
The implementation of this operation uses common request headers. For more information on common request headers, see Common Request Headers.
Special Headers
| Name | Type | Description | Required |
|---|---|---|---|
| Origin | string | Source origin of the simulated cross-origin access | Yes |
| Access-Control-Request-Method | string | HTTP request method of the simulated cross-origin access | Yes |
| Access-Control-Request-Headers | string | Request headers of the simulated cross-origin access | No |
Request Body
The request body of this request is empty.
Response
Response Headers
Common Response Headers
This response contains common response headers. For more information on common response headers, see Common Response Headers.
Special Response Headers
The special response headers used by this operation include:
| Name | Type | Description |
|---|---|---|
| Access-Control-Allow-Origin | string | Source origin of the simulated cross-origin access. This header will not be returned if the origin is not allowed |
| Access-Control-Allow-Methods | string | HTTP request method of the simulated cross-origin access. This header will not be returned if the request method is not allowed |
| Access-Control-Allow-Headers | string | Request headers of the simulated cross-origin access. If any request header is not allowed, it will not be returned by this response header |
| Access-Control-Expose-Headers | string | HTTP request method of the simulated cross-origin access. This header will not be returned if the request method is not allowed |
| Access-Control-Max-Age | string | Sets the validity period of the result of the OPTIONS request |
Response Body
This response body is empty.
Example
Request
OPTIONS /exampleobject HTTP/1.1
Host: examplebucket-1250000000.cos.ap-beijing.myqcloud.com
Date: Thu, 12 Jan 2017 17:26:53 GMT
Origin: http://www.qq.com
Access-Control-Request-Method: PUT
Authorization: q-sign-algorithm=sha1&q-ak=AKIDDNMEycgLRPI2axw9xa2Hhx87wZ3MqQCn&q-sign-time=1487070734;32466654734&q-key-time=1487070734;32559966734&q-header-list=host&q-url-param-list=&q-signature=2ac3ada19910f44836ae0df72a0ec1003f34324bResponse
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: 16087
Connection: keep-alive
x-cos-request-id: NTg3NzRiZGRfYmRjMzVfM2Y2OF81N2YzNA==
Date: Thu, 12 Jan 2017 17:26:53 GMT
ETag: \"9a4802d5c99dafe1c04da0a8e7e166bf\"
Access-Control-Allow-Origin: http://www.qq.com
Access-Control-Allow-Methods: PUT
Access-Control-Expose-Headers: x-cos-request-id
Server: tencent-cos