[2/3 chromium] Support redirect option of Request and "opaqueredirect" response type.

content/browser/loader/resource_loader.cc

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "content/browser/loader/resource_loader.h"
 
 #include "base/command_line.h"
 #include "base/location.h"
 #include "base/metrics/histogram.h"
 #include "base/profiler/scoped_tracker.h"
@@ skipping 262 matching lines @@
       !ChildProcessSecurityPolicyImpl::GetInstance()->
           CanRequestURL(info->GetChildID(), redirect_info.new_url)) {
     DVLOG(1) << "Denied unauthorized request for "
              << redirect_info.new_url.possibly_invalid_spec();
 
     // Tell the renderer that this request was disallowed.
     Cancel();
     return;
   }
 
+  if (info->fetch_redirect_mode() == FETCH_REDIRECT_MODE_ERROR) {
+    Cancel();
+    return;
+  } else if (info->fetch_redirect_mode() == FETCH_REDIRECT_MODE_MANUAL) {
+    CompleteResponseStarted();
+    ResponseCompleted();

[yhirano, 2015/08/10 04:57:52]

You need to read the response body.

[horo, 2015/08/10 06:45:18]

We don't need to read the response body because there is no way to read the body
of opaque-redirect filtered response's internal response.

Added comment.

[yhirano, 2015/08/10 07:03:07]

A fetch API user cannot read the internal response body, but other APIs may read
it.

 "The fetch algorithm returns such a view to ensure APIs do not accidentally
leak information. If the information is required, e.g., to feed image data to a
decoder, the associated internal response can be used, which is only
"accessible" to internal specification algorithms."

[horo, 2015/08/10 07:19:45]

Which API can read the body?

Opaque-redirect filtered responses can be usable only when calling
FetchEvent.respondWith() for navigation requests.
I think navigation requests don't care the body of redirect responses.

[yhirano, 2015/08/10 07:41:20]

I don't know a specific example, but the fetch spec says ANY API can use the
internal response. Even if it is not used by anyone at this moment, someone may
use it in the future.

[horo, 2015/08/10 08:11:59]

I see. I added TODO.

+    return;
+  }
+
   delegate_->DidReceiveRedirect(this, redirect_info.new_url);
 
   if (delegate_->HandleExternalProtocol(this, redirect_info.new_url)) {
     // The request is complete so we can remove it.
     CancelAndIgnore();
     return;
   }
 
   scoped_refptr<ResourceResponse> response(new ResourceResponse());
   PopulateResourceResponse(info, request_.get(), response.get());
@@ skipping 471 matching lines @@
       case net::URLRequestStatus::FAILED:
         status = STATUS_UNDEFINED;
         break;
     }
 
     UMA_HISTOGRAM_ENUMERATION("Net.Prefetch.Pattern", status, STATUS_MAX);
   }
 }
 
 }  // namespace content