Tango->FCM migration. Correct header format in the Registration request.

Bug: 801985
Change-Id: I8ccb1f7d351c143008e0f66bcf06b8561669a006
Reviewed-on: https://chromium-review.googlesource.com/1088697Reviewed-by: Jan Krcal <jkrcal@chromium.org>
Reviewed-by: Pavel Yatsuk <pavely@chromium.org>
Commit-Queue: Tatiana Gornak <melandory@chromium.org>
Cr-Commit-Position: refs/heads/master@{#571053}

components/invalidation/impl/per_user_topic_registration_manager.cc

@@ -141,15 +141,13 @@ void PerUserTopicRegistrationManager::TryToRegisterId(
   }
   PerUserTopicRegistrationRequest::Builder builder;
 
-  it->second->request =
-      builder.SetToken(token_)
-          .SetScope(kInvalidationRegistrationScope)
-          .SetPublicTopicName(id.name())
-          .SetAuthenticationHeader(base::StringPrintf(
-              "%s: Bearer %s", net::HttpRequestHeaders::kAuthorization,
-              access_token_.c_str()))
-          .SetProjectId(kProjectId)
-          .Build();
+  it->second->request = builder.SetToken(token_)
+                            .SetScope(kInvalidationRegistrationScope)
+                            .SetPublicTopicName(id.name())
+                            .SetAuthenticationHeader(base::StringPrintf(
+                                "Bearer %s", access_token_.c_str()))
+                            .SetProjectId(kProjectId)
+                            .Build();
 
   it->second->request->Start(
       base::BindOnce(&PerUserTopicRegistrationManager::RegistrationEntry::