Allow the X-Chrome-Variations header to transmit to all ports.

chrome/browser/google/google_util.h

Index: chrome/browser/google/google_util.h
diff --git a/chrome/browser/google/google_util.h b/chrome/browser/google/google_util.h
index 43bc685e0a279f56a0a49c6d03b7bf3e058606a9..58d150188e3f87efd9fc47ce5b1a49621142210f 100644
--- a/chrome/browser/google/google_util.h
+++ b/chrome/browser/google/google_util.h
@@ -58,14 +58,25 @@ enum SubdomainPermission {
   DISALLOW_SUBDOMAIN,
 };
 
-// True if |url| is an HTTP[S] request with host "[www.]google.<TLD>" and no
-// explicit port. If |permission| is ALLOW_SUBDOMAIN, we check against host
-// "*.google.<TLD>" instead.
-bool IsGoogleDomainUrl(const std::string& url, SubdomainPermission permission);
+// Designate whether or not a URL checking function also checks for standard
+// ports (80 for http, 443 for https), or if it allows all port numbers.

[Ilya Sherman, 2012/08/31 03:05:42]

This isn't quite right -- http://www.google.com:80/ will currently fail the
IsGoogleDomainUrl check, since the code rejects any explicit ports, even if
they're the default ones.

[SteveT, 2012/08/31 13:29:31]

So the GURL code actually parses out port 80 on http URLs, and port 443 on https
URLs. That is to say, even if they're listed explicitly, they're treated as not
being there (the GURL::port() accessor returns an empty string).

So we're actually good to go with http://www.google.com:80/ (see tests... one of
the _old_ test cases tested this)

Does that seem OK? Perhaps I should change the comment in IsGoogleDomainUrl to
be more specific about this?

[Ilya Sherman, 2012/08/31 19:26:52]

Ah, ok, lovely :)
Yeah, I think we should change the comment not to talk about explicit ports
then.

[SteveT, 2012/08/31 21:58:17]

Sounds good!

+enum PortPermission {
+  ALLOW_ALL_PORTS,
+  ALLOW_STANDARD_PORTS,

[Ilya Sherman, 2012/08/31 03:05:42]

nit: Perhaps these should be ALLOW_EXPLICIT_PORTS and DISALLOW_EXPLICIT_PORTS?

[SteveT, 2012/08/31 13:29:31]

See comments above... they sort of explain why I used ALLOW_ALL_PORTS and
ALLOW_STANDARD_PORTS instead of the word EXPLICIT.

[Ilya Sherman, 2012/08/31 19:26:52]

Ok.  I still think it's useful to frame this as allowing or disallowing a
potentially dangerous permission, so perhaps ALLOW_NON_STANDARD_PORTS and
DISALLOW_NON_STANDARD_PORTS?

[SteveT, 2012/08/31 21:58:17]

Done.

+};
+
+// True if |url| is an HTTP[S] request with host "[www.]google.<TLD>". If
+// |subdomain_permission| is ALLOW_SUBDOMAIN, we check against host
+// "*.google.<TLD>" instead. If |port_permission| is ALLOW_STANDARD_PORTS, we
+// disallow explicit ports.

[SteveT, 2012/08/31 13:29:31]

I guess we could change this comment up if the word explicit is misleading, due
to how GURL handles port 80 and 443.

+bool IsGoogleDomainUrl(const std::string& url,
+                       SubdomainPermission subdomain_permission,
+                       PortPermission port_permission);
 // True if |host| is "[www.]google.<TLD>" with a valid TLD. If
-// |permission| is ALLOW_SUBDOMAIN, we check against host "*.google.<TLD>"
-// instead.
-bool IsGoogleHostname(const std::string& host, SubdomainPermission permission);
+// |subdomain_permission| is ALLOW_SUBDOMAIN, we check against host
+// "*.google.<TLD>" instead.
+bool IsGoogleHostname(const std::string& host,
+                      SubdomainPermission subdomain_permission);
 // True if |url| represents a valid Google home page URL.
 bool IsGoogleHomePageUrl(const std::string& url);
 // True if |url| represents a valid Google search URL.