HTML Audio/Video DOM Reference

HTML5 Video azure - Seekbar not working in Chrome Byte serving Byte serving is the process of sending only a portion of an HTTP/1.1 message from a server to a client. Byte serving begins when a HTTP server advertises its willingness to serve partial requests using the Accept-Ranges response header. A client then requests a specific part of a file from the server using the Range request header. If the range is valid, the server sends it to the client with a 206 Partial Content status code and a Content-Range header listing the range sent. If the range is invalid, the server responds with a 416 Requested Range Not Satisfiable status code. Clients which request byte-serving might do so in cases in which a large file has been only partially delivered and a limited portion of the file is needed in a particular range. Section 14.35.2 of RFC 2616 says the client makes Range Retrieval Requests when it makes a partial content requestClients make range requests [2][3]Byte Range Serving[4]Page on demand[5] See also[edit] References[edit] External links[edit]