Reviewed-by: Sabelnikov, Dmitriy <dmitriy.sabelnikov@t-systems.com>
Co-authored-by: zhangyue <zhangyue164@huawei.com>
Co-committed-by: zhangyue <zhangyue164@huawei.com>

2024-08-27 09:16:16 +00:00

8.6 KiB

Raw Blame History

GET Bucket request payment

This API obtains the requester-pays configuration information of a bucket.

Request Syntax

1
2
3
4
5
GET /?requestPayment HTTP/1.1 
Host: bucketname.obs.region.example.com
Date: date
Authorization: authorization
Content-Length: length

Request Parameters

This request involves no parameters.

Request Headers

This request uses common headers. For details about common request headers, see section Common Request Headers.

Request Elements

This request involves no elements.

Response Syntax

1
2
3
4
5
6
7
8
9
HTTP/1.1 status_code
Content-Type: type
Date: date
Content-Length: length

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<RequestPaymentConfiguration xmlns="http://obs.example.com/doc/2015-06-30/">
  <Payer>Payer</Payer>
</RequestPaymentConfiguration>

Response Headers

This response uses common headers. For details about common response headers, see section Common Response Headers.

Response Elements

This response contains the following elements:

Element	Description
RequestPaymentConfiguration	Elements of the requester-pays configuration. Type: element
Payer	Identifier of who pays for the bucket. Type: enumeration Ancestor: RequestPaymentConfiguration Valid values: BucketOwner: The bucket owner pays all fees associated with the bucket. Requester: The requester pays for data transfer and API calls associated with accessing resources in the bucket, while the bucket owner pays for data storage in the bucket.

Element

Description

RequestPaymentConfiguration

Elements of the requester-pays configuration.

Type: element

Payer

Identifier of who pays for the bucket.

Type: enumeration

Ancestor: RequestPaymentConfiguration

Valid values:

BucketOwner: The bucket owner pays all fees associated with the bucket.
Requester: The requester pays for data transfer and API calls associated with accessing resources in the bucket, while the bucket owner pays for data storage in the bucket.

Error Responses

No special error responses are returned. For details about error responses, see Table 1.

Sample Request

GET /?requestPayment HTTP/1.1
User-Agent: curl/7.29.0
Host: examplebucket.obs.region.example.com
Accept: */*
Date: Tue, 03 Mar 2020 12:07:05 GMT
Authorization: authorization

Sample Response

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
HTTP/1.1 200 OK
Server: OBS
x-amz-request-id: 0000016A6C21AD79654C09D9AA45EB5D
x-amz-id-2: 32AAAQAAEAABAAAQAAEAABAAAQAAEAABCSmfq4hegf1QZv8/ewfveE4B566v5DZ8
Content-Type: application/xml
Date: Tue, 30 Apr 2019 02:45:07 GMT
Content-Length: 0

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<RequestPaymentConfiguration xmlns="http://obs.example.com/doc/2015-06-30/">
  <Payer>Requester</Payer>
</RequestPaymentConfiguration>

Parent topic: Operations on Buckets

8.6 KiB Raw Blame History