Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HTTP Range Request Issue #397

Open
GoogleCodeExporter opened this issue Mar 16, 2015 · 0 comments
Open

HTTP Range Request Issue #397

GoogleCodeExporter opened this issue Mar 16, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

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 [email protected] on 23 May 2013 at 4:05

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant