Avoid having every frame of a multipart response create a new

row in the history database.  We do this by setting a flag
on the WebURLResponse created for multipart responses and not
updating the history db when this flag is set.

Take 2, the last landing failed because we weren't always
initializing m_isMultipartPayload in ResourceResponse.

BUG=34350

Review URL: http://codereview.chromium.org/668050

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@40613 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 8 insertions, 1 deletions

diff --git a/webkit/glue/multipart_response_delegate.cc b/webkit/glue/multipart_response_delegate.cc
index 20e207a..8de6469 100644
--- a/webkit/glue/multipart_response_delegate.cc
+++ b/webkit/glue/multipart_response_delegate.cc
@@ -64,7 +64,8 @@ MultipartResponseDelegate::MultipartResponseDelegate(
       boundary_("--"),
       first_received_data_(true),
       processing_headers_(false),
-      stop_sending_(false) {
+      stop_sending_(false),
+      has_sent_first_response_(false) {
   // Some servers report a boundary prefixed with "--".  See bug 5786.
   if (StartsWithASCII(boundary, "--", true)) {
     boundary_.assign(boundary);
@@ -227,6 +228,12 @@ bool MultipartResponseDelegate::ParseHeaders() {
                                   WebString::fromUTF8(value));
     }
   }
+  // To avoid recording every multipart load as a separate visit in
+  // the history database, we want to keep track of whether the response
+  // is part of a multipart payload.  We do want to record the first visit,
+  // so we only set isMultipartPayload to true after the first visit.
+  response.setIsMultipartPayload(has_sent_first_response_);
+  has_sent_first_response_ = true;
   // Send the response!
   client_->didReceiveResponse(loader_, response);