Status: Untriaged Owner: [email protected] CC: [email protected], [email protected] Labels: Type-Bug Pri-2 OS-All Area-Misc Size-Medium Area-BrowserBackend
New issue 22231 by [email protected]: New FTP should handle request with HTTP Range header http://code.google.com/p/chromium/issues/detail?id=22231 The new ftp implementation should handle HTTP range header and replies with a net::ERR_REQUEST_RANGE_NOT_SATISFIABLE error. HTML elements like <video> and <audio> are protocol agnostic, meaning that they would pass along whatever src they receive to the browser process. There is one thing particular in HTTP protocol used by such elements that they use "Range:" header to request ranges, and they would submit such request for whatever src they receive. It mean that, in the case of <audio> or <video>, the network backend needs to understand this "Range" header. Right now http:// and file:// has it implemented but not ftp://, we don't need full implementation for this request but need to at least know how to fail. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
