Add cross origin to Blink-driven preconnect

chrome/browser/net/preconnect.h

 // 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.
 
 // A Preconnect instance maintains state while a TCP/IP connection is made, and
 // and then released into the pool of available connections for future use.
 
 #ifndef CHROME_BROWSER_NET_PRECONNECT_H_
 #define CHROME_BROWSER_NET_PRECONNECT_H_
 
@@ skipping 16 matching lines @@
                           int count,
                           net::URLRequestContextGetter* getter);
 
 // Try to preconnect.  Typically used by predictor when a subresource probably
 // needs a connection. |count| may be used to request more than one connection
 // be established in parallel.
 void PreconnectOnIOThread(const GURL& url,
                           const GURL& first_party_for_cookies,
                           UrlInfo::ResolutionMotivation motivation,
                           int count,
-                          net::URLRequestContextGetter* getter);
+                          net::URLRequestContextGetter* getter,
+                          bool allow_credentials);

[Ryan Sleevi, 2015/07/10 09:46:45]

Wondering out loud (for Matt, mostly) - do we want this to be an enum?

like

chrome_browser_net {

enum CredentialsFlag {
  CREDENTIALS_FLAG_SET,
  CREDENTIALS_FLAG_UNSET,
};


Bikeshed on naming (INCLUDE_CREDENTIALS, etc) notwithstanding, my goal was to
see if it makes it clearer how this maps back to Fetch spec terminology (namely,
"credentials flag" as discussed in
https://fetch.spec.whatwg.org/#http-network-or-cache-fetch ) so that it can be
clear how this is used.

 
 }  // namespace chrome_browser_net
 
 #endif  // CHROME_BROWSER_NET_PRECONNECT_H_