Naming Issue? 3

[soulcyon]

http://code.google.com/p/chromium/issues/detail?id=100011

As per the ticket above, if the Content-disposition header has the [comma] symbol, then Chrome will throw a "Duplicate headers received from server" error.

I tried streaming a video file with a [comma] in the filename, and I've reproduced this "bug". For a temporary fix, I modified index.js like this:

info.file = info.path.match(/*...*/).replace(",", "%2C");

[soulcyon]

It seems that info.file variable isn't really used anywhere else, so I modified the variable itself right at the top.

I suggest that the ".replace" fix be implemented only for the Content-Disposition declaration.

[meloncholy]

At least this one isn't my fault. :) I need to leave now, but I'll use your fix tomorrow. Thanks!

[soulcyon]

No problem!

After a bit testing, it seemed you were missing quotes after filename=