The GET container consistency request allows you to determine the consistency level being applied to a particular container.
Request
| Request HTTP Header |
Description |
|---|
| X-Auth-Token |
Specifies the Swift authentication token for the account to use for the request. |
| x-ntap-sg-consistency |
Specifies the type of request, where true = GET container consistency, and false = GET container. |
| Host |
The hostname to which the request is directed. |
Request example
GET /v1/28544923908243208806/<Swift container> HTTP/1.1
x-ntap-sg-consistency: true
X-Auth-Token: SGRD_3a877009a2d24cb1801587bfa9050f29
Host: test.com
Response
| Response HTTP Header |
Description |
|---|
| Date |
The date and time of the response. |
| Connection |
Specifies whether the connection to the server is open or closed. |
| X-Trans-Id |
The unique transaction identifier for the request. |
| Content-Length |
The length of the response body. |
| x-ntap-sg-consistency |
Specifies the consistency control level being applied to the container. The following values are supported:- all: Provides the highest consistency guarantee. All nodes receive the data immediately or the request will fail.
- strong-global: Guarantees a consistent read-after-write view for all operations across all sites.
- strong-site: Guarantees a consistent read-after-write view for all operations within a site.
- weak: Ensures the highest availability, but provides no consistency guarantees and a reduced guarantee of data protection.
- default: Eventually consistent, highly available, with data protection guarantees.
|
Response example
HTTP/1.1 204 No Content
Date: Sat, 29 Nov 2015 01:02:18 GMT
Connection: CLOSE
X-Trans-Id: 1936575373
Content-Length: 0
x-ntap-sg-consistency: strong-site