Remove WebURLRequest::initialize() and simplify WebURLRequest

content/renderer/fetchers/resource_fetcher_impl.cc

Index: content/renderer/fetchers/resource_fetcher_impl.cc
diff --git a/content/renderer/fetchers/resource_fetcher_impl.cc b/content/renderer/fetchers/resource_fetcher_impl.cc
index 51878491e6a3403494189701d3ba69008ed89fe2..3c23271e2661e938a2dd456b1c196b659528f7ba 100644
--- a/content/renderer/fetchers/resource_fetcher_impl.cc
+++ b/content/renderer/fetchers/resource_fetcher_impl.cc
@@ -122,8 +122,8 @@ void ResourceFetcherImpl::Start(
   }
   loader_->loadAsynchronously(request_, this);
 
-  // No need to hold on to the request.
-  request_.reset();
+  // Reset the request.
+  request_.setURL(GURL());

[dcheng, 2016/07/11 09:47:50]

It's a bit unexpected that this is the right way to 'reset' the request. This
would leave all the other state on the WebURLRequest as-is, right? I'm guessing
that's probably OK, but it's not the easiest for someone who doesn't know the
code (like me =) to understand.

Do you think it's worth writing this as request_ = WebURLRequest() instead, or
still providing a reset() method that does the same?

[kinuko, 2016/07/11 09:54:23]

Yup you're right this change is probably not quite right... I wondered if I
should do this or that.  Let me think about it and update.

[kinuko, 2016/07/12 04:19:57]

Took the path to simply do request_ = WebURLRequest().

 }
 
 void ResourceFetcherImpl::SetTimeout(const base::TimeDelta& timeout) {