Set the target type when creating the request for main resource

Source/platform/network/ResourceRequest.h

Index: Source/platform/network/ResourceRequest.h
diff --git a/Source/platform/network/ResourceRequest.h b/Source/platform/network/ResourceRequest.h
index cb1e7c5a304ac3ff2ce127a54be4f5134dc570e2..5fd376d6900cc927676773f7d835874a1ccbb252 100644
--- a/Source/platform/network/ResourceRequest.h
+++ b/Source/platform/network/ResourceRequest.h
@@ -99,6 +99,12 @@ public:
         setHTTPReferrer(referrer);
     }
 
+    // Factory methods that should be used when creating a ResourceRequest for a
+    // main resource.
+    static ResourceRequest createMainResourceRequest(const KURL&, bool isMainFrame);

[Nate Chapin, 2014/06/24 18:28:54]

Why is it better to have these static factory methods instead than constructors
(like the other ways to create a ResourceRequest)?

[clamy, 2014/06/25 15:47:11]

I thought it was more explicit that they give you a ResourceRequest that should
only be used for main resources. But it doesn't fit very well with the rest of
the code which uses constructors. So I made a new patch set with constructors,
so that we only have one way to create a ResourceRequest.

+    static ResourceRequest createMainResourceRequest(
+        const KURL&, bool isMainFrame, const Referrer&, ResourceRequestCachePolicy = UseProtocolCachePolicy);
+
     static PassOwnPtr<ResourceRequest> adopt(PassOwnPtr<CrossThreadResourceRequestData>);
 
     // Gets a copy of the data suitable for passing to another thread.
@@ -217,6 +223,8 @@ public:
 private:
     void initialize(const KURL& url, ResourceRequestCachePolicy cachePolicy);
 
+    void setTargetTypeForMainResource(bool isMainFrame);
+
     const CacheControlHeader& cacheControlHeader() const;
 
     KURL m_url;