Upload one chunk

Send one chunk as the raw request body. Chunks are idempotent and may be sent concurrently and out of order, but only within the receiving window [frontier, frontier+8), which slides forward as the driver consumes data. Every chunk except the last must be exactly chunk_size bytes; the last one is the remainder. When the window is full the request parks on the server for up to 10 seconds waiting for a free slot before answering 429. If the session already completed (e.g. rapid upload) the chunk is absorbed idempotently and the returned snapshot has state=completed — stop sending the remaining chunks. The server always consumes the request body before answering, so browsers never see an early response.

返回响应

🟢200Success

application/json

Chunk stored (or absorbed idempotently); data is the latest session snapshot

Bodyapplication/json

示例

{
    "code": 200,
    "message": "success",
    "data": {
        "upload_id": "3f2c9e2a-6c4b-4d2e-9a2b-1f0e8c7d5a41",
        "state": "receiving",
        "attempt": 0,
        "path": "/uploads/movie.mkv",
        "size": 734003200,
        "chunk_size": 10485760,
        "total_chunks": 70,
        "received": [
            [
                0,
                11
            ]
        ],
        "received_bytes": 125829120,
        "frontier": 9,
        "storage_progress": 12.86
    }
}

🟠400Bad Chunk or Failed Session

🟠401Unauthorized

🟠403Not Owner

🟠404Session Not Found

🟠409Chunk In Flight

🟠429Window Full

请求参数

请求示例代码

返回响应