         | Did this page help you? Yes No Tell us about it... |
Range GETs
If an object is large, the end user might want to break up the download into smaller units. To do this, the end user sends multiple range GET requests, each specifying a different byte range to GET. If the object is already present in the edge location, CloudFront serves the part from the edge location (regardless of the byte range specified).
If the object is not already present (partially or entirely) in the edge location, the behavior varies if the request is for the first part of the object or a later part:
First part of the object—CloudFront gets the whole object from the origin
CloudFront goes to the origin and starts to copy the entire object to the edge location. As soon as the first byte appears at the edge location, CloudFront starts to serve the part to the end user. CloudFront then continues to copy the entire object to the edge location to satisfy subsequent GET requests.
Later part of the object—CloudFront gets just the designated part from the origin
CloudFront goes to the origin and copies only the requested part to the edge location. As soon as the first byte of the part appears at the edge location, CloudFront starts to serve the part to the end user. After the part is completely served, it does not remain in the edge location.
