Dell DX6004S DX Object Storage SCSP Proxy Overview - Page 9

response body. Similar to the individual Info method, the response for a successful AggregateInfo method execution is a 200 code. The following is a sample checkpoint manifest stream. All object names must be URL-encoded so you must use percent encoding to escape special characters in named objects, including space. All line terminators must be CRLF: 1C1AF51688DA4F752CD26E6CD115A6A5 mybucket/photos/marketing/photo.jpg 2AC1961A54575A82CCE115D8F1DA6D6F 12BFEA648C2697A56FD5618CAE15D5CA training/cloudstorage/videos/mobile/named-objects.3gp /samples/object%20with%20space.txt 5AE562AC876418F612AA511CDD69F5CD mutable 5DA58EAC74129D116625C611AF5A86DF The checkpoint manifest should be stored in the local cluster and its name or UUID used to issue the AggregateInfo request. The AggregateInfo method supports named and unnamed objects for both the manifests and streams stored in the manifest. It supports authentication only for the manifest stream itself, and checkpoint streams in the manifests that are protected for HEAD are returned as 401s in the AggregateInfo response body. Any additional query arguments and headers included with the AggregateInfo method apply to the GET request issued for the checkpoint manifest only and are not included in the individual Info requests for each name or UUID in the manifest. If the checkpoint manifest is stored in an unnamed anchor stream, the AggregateInfo method must be called with alias=yes in its queryArg dictionary. AggregateInfo uses Aggregate-Stream-Count as its trailer header. Expect: Content-MD5 and Range headers, as well as any integrity seal query arguments, are not supported for the AggregateInfo method. 1.2.3.1. Aggregate Info Response For each line of the checkpoint manifest, the SCSP Proxy uses chunked encoding to send in the AggregateInfo response body either a parse error for the line or the line's name or UUID followed by the DX Storage's verbatim response for the Info query for it. A CRLF line-end sequence separates the uuid line from the Info response. For example, for a manifest that included two UUIDs, both of which the SDK was able to Info successfully, the following representative response body would be returned: Response for stream uuid = 64f9e40bfcb7046d79cc02c5876c1904 HTTP/1.1 200 OK Castor-System-Alias: 64f9e40bfcb7046d79cc02c5876c1904 Castor-System-Cluster: DR Cluster Castor-System-Created: Tue, 03 Aug 2010 18:49:27 GMT Castor-System-Version: 1280861367.827 Content-Length: 11 Content-Type: application/x-www-form-urlencoded Last-Modified: Tue, 03 Aug 2010 18:49:27 GMT Etag: "aa9ba7fb4648f05c21411cce06c7c3d5" Date: Tue, 03 Aug 2010 18:49:28 GMT Server: CAStor Cluster/4.0.2 Copyright © 2010 Caringo, Inc. All rights reserved 6 Version 1.2 December 2010