Download Files
Last update：2025-08-18 15:32:05
This interface provides the capability to download specified resource files from the object storage platform, supporting standard HTTP file download protocols, which meet the needs of various resource distribution scenarios.
Request Description
Basic Request Format
File downloads use the standard HTTP GET specification. See the RFC2616 Standard for details.
http://< domain>/< key>?< param1>=< value1>&< param2>=< value2>...
Segmented Download Request Format
During a download, the standard HTTP Range request header can be used to support the multipart download and resuming upload from breakpoint.
Range: bytes=< first-byte>-< last-byte>
- Assuming the file has a total length of 1000 bytes, different Range values will result in different response behaviors, as shown below:
| Range Header | Response Description | Status Code |
|---|---|---|
Range: bytes=0-888 |
Returns bytes 0–888 (a total of 889 bytes) | 206 Partial Content |
Range: bytes=666-888 |
Returns bytes 666–888 (a total of 223 bytes) | 206 Partial Content |
Range: bytes=-888 |
Returns the last 888 bytes of the file | 206 Partial Content |
Range: bytes=-1888 (End offset exceeds file size) |
Returns the entire file (a total of 1000 bytes) | 206 Partial Content |
Range: bytes=666- |
Returns bytes from position 666 to the end of the file (334 bytes) | 206 Partial Content |
Range: bytes=1-1888 (End offset exceeds file size) |
Returns bytes from position 1 to the end of the file | 206 Partial Content |
Range: bytes=1666-1888 (Start offset exceeds file size) |
No content is returned | 416 Requested Range Not Satisfiable |
Range: bytes=888-666 (Start offset greater than end offset) |
No content is returned | 416 Requested Range Not Satisfiable |
Range: bytes=-a888- (Invalid range format) |
No content is returned | 416 Requested Range Not Satisfiable |
Response Description
Standard Download Response
Response of the download request should conform to the HTTP GET request specification. See the RFC2616 Standard for details.
Special Headers for Append-Uploaded Objects
For an object append-uploaded, the following two headers will be added during response:
x-wcs-object-type: Appendable
x-next-append-position: < Content-Length int64>
The above two headers are used to identify the type of object and position of the next append.
Example
curl -v -o 1.png http://downloadDomain/1.png