This operation allows a bucket owner to get the versioning status of the bucket.
If versioning is not configured for a bucket, no versioning status information will be returned following this operation.
1 2 3 4 | GET /?versioning HTTP/1.1 Host: bucketname.obs.region.example.com Date: date Authorization: authorization |
This request contains no message parameters.
This request uses common headers. For details, see Table 3.
This request involves no elements.
1 2 3 4 5 6 7 8 | HTTP/1.1 status_code Date: date Content-Type: type Content-Length: length <VersioningConfiguration xmlns="http://obs.region.example.com/doc/2015-06-30/"> <Status>status</Status> </VersioningConfiguration> |
The response to the request uses common headers. For details, see Table 1.
This response contains elements to specify the bucket versioning status. Table 1 describes the elements.
No special error responses are returned. For details about error responses, see Table 2.
1 2 3 4 5 6 | GET /?versioning HTTP/1.1 User-Agent: curl/7.29.0 Host: examplebucket.obs.region.example.com Accept: */* Date: WED, 01 Jul 2015 03:15:20 GMT Authorization: OBS H4IPJX0TQTHTHEBQQCEC:4N5qQIoluLO9xMY0m+8lIn/UWXM= |
1 2 3 4 5 6 7 8 9 10 11 12 | HTTP/1.1 200 OK Server: OBS x-obs-request-id: BF260000016436BBA4930622B4FC9F17 x-obs-id-2: 32AAAQAAEAABAAAQAAEAABAAAQAAEAABCSQIrNJ5/Ag6EPN8DAwWlPWgBc/xfBnx Content-Type: application/xml Date: WED, 01 Jul 2015 03:15:20 GMT Content-Length: 180 <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <VersioningConfiguration xmlns="http://obs.example.com/doc/2015-06-30/"> <Status>Enabled</Status> </VersioningConfiguration> |