Considerations when using "download"
If using "download" with ObjectStore (NS4), the following considerations apply.
Downloads of huge objects
When downloading huge objects (typically any file in excess of 2 GB in size), be prepared to retry the HTTP request if the TCP connection fails. With a retry, ensure that you perform the following:
- Update the Authentication Signature Header: The previous one may have expired.
- Incorporate a Byte Range Request that Begins from the Point the Failure: This will ensure forward progress. This is especially helpful when the token associated with Authentication Signature Header has expired, and NetStorage is trying to transparently retrieve the latter part of the object from a different system in the network.
- Only Construct Full Objects from Partial Byte Range Responses that Use the Same “ETag” Response Header Value: This will help if the object has changed between requests. Otherwise, at least check that the full object reports the same “md5” value in one of the Etag response headers.
Downloads and byte range requests
Byte Range requests are honored as long as the HTTP “Range” header consists of a single, closed range (number-number). Support for multiple ranges and the other standard formats for specifying ranges may be added in a future release.
Large quantities of files may affect your downloads
While there is no set maximum on the number of files that can be downloaded using this action, it is important to note that the tool is not intended for use as a “mass download” resource. If used to download a large quantity of files in a single call, you may notice performance issues, and possibly failures.
If you intend to download a large quantity of files, it is recommended that you incorporate an Akamai Delivery Configuration and incorporate Large File Optimization. (Contact your Account Representative for more details.)