Register application connections under their post-redirect URL.

shell/application_manager/network_fetcher.cc

Index: shell/application_manager/network_fetcher.cc
diff --git a/shell/application_manager/network_fetcher.cc b/shell/application_manager/network_fetcher.cc
index a4a5e8aac69e2e5c1eb5bddbb2573f85bac97ad2..f1af41999f2a98cef731c6a4842178ffc6b480bf 100644
--- a/shell/application_manager/network_fetcher.cc
+++ b/shell/application_manager/network_fetcher.cc
@@ -39,6 +39,20 @@ NetworkFetcher::~NetworkFetcher() {
     base::DeleteFile(path_, false);
 }
 
+const GURL& NetworkFetcher::GetURL() const {
+  return url_;
+}
+
+GURL NetworkFetcher::GetRedirectURL() const {
+  if (!response_)
+    return GURL::EmptyGURL();
+
+  if (response_->redirect_url.is_null())
+    return GURL::EmptyGURL();
+
+  return GURL(response_->redirect_url);

[qsr, 2015/02/25 14:50:27]

Did you test this?

The doc for those fields are:

  // These fields are set to non-NULL if this response corresponds to a
  // redirect.  Call the |FollowRedirect| method on the URLLoader instance to
  // follow this redirect.
  string? redirect_method;
  string? redirect_url;

 So my understanding is that if you ask the url loader to follow redirect, it
will handle those by himself, and those fields would always be null. If you want
to use those, you need to handle redirect by yourself (and as you said, I think
this is exactly what we should do anyway)

[Aaron Boodman, 2015/02/25 18:43:08]

Ah, you are right. Fixed.

+}
+
 URLResponsePtr NetworkFetcher::AsURLResponse(base::TaskRunner* task_runner,
                                              uint32_t skip) {
   if (skip != 0) {