For prerendering, keep track of all the intermediate redirects, and hook into...

chrome/browser/prerender/prerender_manager.h

Index: chrome/browser/prerender/prerender_manager.h
===================================================================
--- chrome/browser/prerender/prerender_manager.h	(revision 71174)
+++ chrome/browser/prerender/prerender_manager.h	(working copy)
@@ -7,6 +7,7 @@
 #pragma once
 
 #include <list>
+#include <vector>

[cbentzel, 2011/01/12 23:49:53]

Should a set be used instead of a vector? It seems like a vector is fine even if
there is a finite redirect loop, but curious about what you think.

[tburkard, 2011/01/13 19:14:16]

I don't think it makes a difference..
formally set would do but since it's so small vector might be more efficient.
On 2011/01/12 23:49:53, cbentzel wrote:

[cbentzel, 2011/01/14 02:01:13]

Seems reasonable. 

 
 #include "base/ref_counted.h"
 #include "base/scoped_ptr.h"
@@ -26,8 +27,9 @@
   // Owned by a Profile object for the lifetime of the profile.
   explicit PrerenderManager(Profile* profile);
 
-  // Preloads the URL supplied.
-  void AddPreload(const GURL& url);
+  // Preloads the URL supplied.  alias_urls indicates URLs that redirect
+  // to the same URL to be preloaded.
+  void AddPreload(const GURL& url, const std::vector<GURL>& alias_urls);
 
   // For a given TabContents that wants to navigate to the URL supplied,
   // determines whether a preloaded version of the URL can be used,