Common Headers
更新时间：2022-03-01 18:22:26
Common Request Header
| Header | Description |
|---|---|
| Authorization | The requested identity verification is used to verify the legitimacy of the requester's identity. Anonymous requests do not need to be carried. Type: String Default value: None |
| Content-Length | The length of the message (not including the message header) defined in RFC 2616. All PUT operations must be carried. Type: String Default value: None |
| Content-Type | The type of resource content, for example: text/plain. Type: String Default value: None |
| Content-MD5 | The 128-bit MD5 digest of the message (not including the message header) needs to be Base64 encoded. Type: String Default value: None |
| Date | The current date and time of the request originator. When Authorization is included in the request, the header Date or x-wos-date must be defined in the request. Type: String Default value: None |
| Host | Indicates the host address. Type: String Default value: None |
| Expect | When your request uses 100-continue, the client will not send the request message body until it receives the confirmation from the server. If the request is rejected, the request message body will not be sent. Valid value: 100-continue |
| x-wos-date | The current date and time of the request originator. When Authorization is included in the request, the header Date or x-wos-date must be defined in the request. If the header Date and x-wos-date are defined at the same time in the request, the header x-wos-date is the main one. Type: String Recognized value: None |
Common Response Header
| Name | Description |
|---|---|
| Authorization | The requested identity verification is used to verify the legitimacy of the requester's identity. Anonymous requests do not need to be carried. Type: String Default value: None |
| Content-Length | The length of the message (not including the message header) defined in RFC 2616. All PUT operations must be carried. Type: String Default value: None |
| Content-Type | The type of resource content, for example: text/plain. Type: String Default value: None |
| Content-MD5 | The 128-bit MD5 digest of the message (not including the message header) needs to be Base64 encoded. Type: String Default value: None |
| Date | The current date and time of the request originator. When Authorization is included in the request, the header Date or x-wos-date must be defined in the request. Type: String Default value: None |
| Host | Indicates the host address. Type: String Default value: None |
| Expect | When your request uses 100-continue, the client will not send the request message body until it receives the confirmation from the server. If the request is rejected, the request message body will not be sent. Valid value: 100-continue |
| x-wos-date | The current date and time of the request originator. When Authorization is included in the request, the header Date or x-wos-date must be defined in the request. If the header Date and x-wos-date are defined at the same time in the request, the header x-wos-date is the main one. Type: String Default value: None |
| x-wos-request-id | Created by WOS, the value that uniquely identifies this request, and the problem can be located through this value. Type: String Default value: None |
| Access-Control-Allow-Origin | When the bucket where the object is located is configured with CORS rules, if the requested Origin meets the specified CORS rules, this Origin will be included in the response. Type: String |
| Access-Control-Allow-Methods | When the bucket where the object is located is configured with CORS rules, if the requested Access-Control-Request-Method meets the specified CORS rules, the allowed Methods will be included in the response. Type: String |
| Access-Control-Max-Age | When the bucket where the object is located is configured with CORS rules, if the request meets the CORS rules configured by the bucket, MaxAgeSeconds will be included in the response. Type: Integer |
| Access-Control-Allow-Headers | When the bucket where the object is located is configured with CORS rules, these headers will be included in the response if the request meets the specified CORS rules. Type: String |
| Access-Control-Expose-Headers | Indicates a list of headers that allow access to client-side JavaScript programs. When the bucket where the object is located is configured with CORS rules, if the request meets the specified CORS rules, the ExposeHeader will be included in the response. Type: String |
本篇文档内容对您是否有帮助？
有帮助
我要反馈