From 943b2925ce99deafb646573cf146c63dac2f33e4 Mon Sep 17 00:00:00 2001 From: "ananta@chromium.org" Date: Wed, 17 Dec 2008 17:24:13 +0000 Subject: Handle HTTP 200 responses received in response to byte range requests issued by the plugin. This means that the server does not support byte range requests. Firefox handles this by destroying the current plugin instance and creating a new instance to handle the response. The stream which is created to pass the data off to the plugin is not seekable.Fix is to emulate Firefox behavior. Will work on unit testing the NPN_RequestRead related code in a separate CB. This fixes http://code.google.com/p/chromium/issues/detail?id=5403Bug=5403 Review URL: http://codereview.chromium.org/14122 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@7139 0039d316-1c4b-4281-b951-d872f2087c98 --- chrome/plugin/webplugin_delegate_stub.cc | 1 + 1 file changed, 1 insertion(+) (limited to 'chrome/plugin') diff --git a/chrome/plugin/webplugin_delegate_stub.cc b/chrome/plugin/webplugin_delegate_stub.cc index 11703b6..1fc89cb 100644 --- a/chrome/plugin/webplugin_delegate_stub.cc +++ b/chrome/plugin/webplugin_delegate_stub.cc @@ -157,6 +157,7 @@ void WebPluginDelegateStub::OnDidReceiveResponse( params.headers, params.expected_length, params.last_modified, + params.request_is_seekable, cancel); } -- cgit v1.1