I implemented a very minimal proof of concept that supports part of the WebDAV protocol. This includes the verbs OPTIONS , PROPFIND and GET HTTP. Thus, the built-in Windows WebDAV client (in Windows 8.1) can open a shared resource, a list of WebDAV files and directories, and navigate through them.
The implementation of the HTTP GET verb provides Accept-Ranges (as bytes), Content-Length , Content-Type and Transfer-Encoding (as fragments). When you open a large video file in a browser, it will start playing immediately while it downloads the remaining content. It seems that the built-in WebDAV client for Windows downloads the entire file to a temporary location before the media player plays the file. When the file is 10 GB, it will suck.
Is there a way to provide support so that the embedded WebDAV client can read byte ranges for streaming (I would suggest that you just need to translate to use Range somehow ...)?
Roel van uden
source share