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

1 files changed, 4 insertions, 1 deletions

diff --git a/webkit/glue/plugins/plugin_stream.h b/webkit/glue/plugins/plugin_stream.h
index 7b1250f..5cdc5b4 100644
--- a/webkit/glue/plugins/plugin_stream.h
+++ b/webkit/glue/plugins/plugin_stream.h
@@ -39,10 +39,13 @@ class PluginStream : public base::RefCounted<PluginStream> {
   // mime-types table and the extension (if any) in the URL.
   // If the size of the stream is known, use length to set the size.  If
   // not known, set length to 0.
+  // The request_is_seekable parameter indicates whether byte range requests
+  // can be issued on the stream.
   bool Open(const std::string &mime_type,
             const std::string &headers,
             uint32 length,
-            uint32 last_modified);
+            uint32 last_modified,
+            bool request_is_seekable);
 
   // Writes to the stream.
   int Write(const char *buf, const int len, int data_offset);