None of the reaches in the request’s Range header field cover the present degree of the chose asset or that the arrangement of extents mentioned has been dismissed because of invalid ranges or an unreasonable request of little or covering ranges. 

For byte ranges, neglecting to cover the present degree implies that the main byte-pos of the entirety of the byte-extend spec esteems were more prominent than the present length of the chose representation. At the point when this status code is produced in light of a byte-run demand, the sender SHOULD create a Content-Range header field indicating the present length of the chose representation. 

For instance: 

HTTP/1.1 416 Range Not Satisfiable 

Date: Fri, 20 Jan 2012 15:41:54 GMT 

Content-Range: bytes */47022 

Note: Because servers are allowed to overlook Range, numerous executions will basically react with the whole chosen representation in a 200 OK reaction. That is halfway in light of the fact that most customers are set up to get a 200 OK to finish the errand (but less proficiently) and somewhat on the grounds that customers probably won’t quit making an invalid fractional request until they have gotten a total representation. In this manner, customers can’t rely upon accepting a 416 Range Not Satisfiable reaction in any event, when it is generally suitable.

Leave a Reply