When a user logs into sync, the appropriate cookies are retrieved so that

chrome/browser/chromeos/login/issue_response_handler.cc

Index: chrome/browser/chromeos/login/issue_response_handler.cc
===================================================================
--- chrome/browser/chromeos/login/issue_response_handler.cc	(revision 89672)
+++ chrome/browser/chromeos/login/issue_response_handler.cc	(working copy)
@@ -25,8 +25,7 @@
     const std::string& to_process,
     URLFetcher::Delegate* catcher) {
   VLOG(1) << "Handling IssueAuthToken response";
-  token_url_.assign(base::StringPrintf("%s%s",
-      GaiaUrls::GetInstance()->token_auth_url().c_str(), to_process.c_str()));
+  token_url_.assign(BuildTokenAuthUrlWithToken(to_process));
   URLFetcher* fetcher =
       new URLFetcher(GURL(token_url_), URLFetcher::GET, catcher);
   fetcher->set_load_flags(net::LOAD_DO_NOT_SEND_COOKIES);
@@ -38,4 +37,16 @@
   return fetcher;
 }
 
+// static
+std::string IssueResponseHandler::BuildTokenAuthUrlWithToken(
+    const std::string& token) {
+  const char kUrlFormat[] = "%s?"
+                            "continue=http://www.google.com/webhp&"
+                            "source=chromeos&"
+                            "auth=%s";
+  return base::StringPrintf(kUrlFormat,

[Chris Masone, 2011/06/21 01:26:31]

Why aren't you using GaiaAuthFetcher::MakeTokenAuthBody() here?

[Roger Tawa OOO till Jul 10th, 2011/06/21 03:21:13]

All the GaiaAuthFetcher::MakeXxxBody() functions are private.  The TokenAuth API
accepts its parameters in the body or in the URL, both ways are equivalent.  I
did not want to disturb this code path, so the code is equivalent to the way it
was previously.

+                            GaiaUrls::GetInstance()->token_auth_url().c_str(),
+                            token.c_str());
+}
+
 }  // namespace chromeos