Fix doodle verification URL.

components/search_provider_logos/logo_tracker_unittest.cc

Index: components/search_provider_logos/logo_tracker_unittest.cc
diff --git a/components/search_provider_logos/logo_tracker_unittest.cc b/components/search_provider_logos/logo_tracker_unittest.cc
index c32df2afd8b0b3f027b4836a6c69c3e31f3d1e6b..d3dccbec2b0cdc7ad6b6940df6c92f4f986843ba 100644
--- a/components/search_provider_logos/logo_tracker_unittest.cc
+++ b/components/search_provider_logos/logo_tracker_unittest.cc
@@ -371,8 +371,8 @@ void LogoTrackerTest::SetServerResponseWhenFingerprint(
     const std::string& response_when_fingerprint,
     net::URLRequestStatus::Status request_status,
     net::HttpStatusCode response_code) {
-  GURL url_with_fp =
-      net::AppendQueryParameter(logo_url_, "async", "es_dfp:" + fingerprint);
+  GURL url_with_fp = net::AppendQueryParameter(logo_url_, "async", "es_dfp");
+  url_with_fp = GURL(url_with_fp.spec() + ":" + fingerprint);

[mmenke, 2014/09/23 21:16:17]

This seems really ugly.

You're basically relying on GURL's escaping behavior being different from net's
(Which itself is hideous).  net's behavior looks to be the more correct one here
- RFC 2396 (https://www.ietf.org/rfc/rfc2396.txt) pretty clearly indicates the
colon is reserved in the query component.

Of course, "fixing" GURL here may well break a bunch of sites, so it may make
more sense to "fix" escape.h instead, ideally by making it wrap the GURL code. 
This could cause unexpected regressions as well, however, so I don't think
either option is a merge candidate.

I don't suppose we could just fix the server code?

   fake_url_fetcher_factory_.SetFakeResponse(
       url_with_fp, response_when_fingerprint, response_code, request_status);
 }