3.2.5.2.6 FRAGMENT REQUEST

If the start offset of Content-Range received as part of the current fragment is not the start offset of the next block of data that the server receives, the server MUST return a response as described in section 2.2.7 with HTTP status code 416 and with BITS-Received-Content-Range as the start offset that the client MUST send as part of the next fragment request.

All the rules described in [RFC2616] section 14.16 related to Content-Range would apply while the Content-Range header value received from the client is being processed. The server MUST return a response as described in section 2.2.7 with HTTP status code 400 and with BITS-Error as x80070057, BITS-Error-Context as 0x5.

The server MUST send the response as described in section 2.2.7. The BITS-Error-Context MUST be returned as 0x7 if an error was returned from the back-end client.