So it turns out it was a problem with the headers. I'd stupidly calculated the file length in the header as info.end - info.start, whereas of course it's 1 more than that. This apparently tripped up some browsers but not others.
Thanks so much for pointing me in that direction! On Friday, 20 April 2012 17:07:55 UTC+1, Andrew Weeks wrote: > > Thanks for that - I'll update the code. Unfortunately it won't solve it as > that bit of code is only called when there's a range request in the header, > which isn't true for the linked site. > > On Friday, 20 April 2012 16:06:13 UTC+1, Oliver Leics wrote: >> >> This line: >> https://github.com/meloncholy/vid-streamer/blob/master/index.js#L214 >> header["Content-Range"] = "bytes " + info.length + "/" + info.size; >> >> should be: >> header["Content-Range"] = "bytes " + info.start + "-" + info.end + "/" >> + info.size; >> >> But I don't know if this solves the problem. >> >> -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
