...
Attempting to store an object larger than 4TB will result results in a 400 an HTTP 400 Bad Request response immediately after the write is submitted.
...
Streaming media is supported using industry-standard chunked transfer encoding. Your application can now stream digital media or other types of data to the cluster without knowing the object size in advance. The size of the object is limited only by the available space in the cluster (up to 4TB). Attempting to store a chunked encoded object larger than 4TB will result results in a 400 an HTTP 400 Bad Request response (see note above).
Any object written with HTTP chunked transfer encoding must be erasure-coded and cannot be replicated. If you write an object and specify both erasure coding and replication in the header (for example, combining an encoding=5:2 query argument with a lifepoint header with a reps= parameter), the write operation will result results in a 400 an HTTP 400 Bad Request response.