What steps will reproduce the problem?
1. use a browser (Chrome 26) to play a large wav file (>10M) through mongoose
2. the browser loads the build-in player and request audio file in parts with
"Range" headers
What is the expected output? What do you see instead?
I want chrome to play the audio file, but it didn't
What version of the product are you using? On what operating system?
I use the latest mongoose 3.7 and it runs on Windows 8 Pro 64bit
Please provide any additional information below.
Range request will not be handled if the browser sends the "Range" header like
this
Range: bytes=512-
I think range header is not parsed correctly in the function
'handle_file_request'
Original issue reported on code.google.com by a6905...@gmail.com on 23 May 2013 at 4:05
Original issue reported on code.google.com by
a6905...@gmail.comon 23 May 2013 at 4:05