[ChromeOS] Make GaiaAutheFetcher parsing logic default to service_unavailable

chrome/common/net/gaia/gaia_auth_fetcher.cc

Index: chrome/common/net/gaia/gaia_auth_fetcher.cc
diff --git a/chrome/common/net/gaia/gaia_auth_fetcher.cc b/chrome/common/net/gaia/gaia_auth_fetcher.cc
index ec6e808cab7ca62d8520b11caa091767e35ed5d7..0499168bf8043d05525d2efc159d3405bdf32921 100644
--- a/chrome/common/net/gaia/gaia_auth_fetcher.cc
+++ b/chrome/common/net/gaia/gaia_auth_fetcher.cc
@@ -53,6 +53,8 @@ const char GaiaAuthFetcher::kAccountDeletedError[] = "AccountDeleted";
 // static
 const char GaiaAuthFetcher::kAccountDisabledError[] = "AccountDisabled";
 // static
+const char GaiaAuthFetcher::kBadAuthenticationError[] = "BadAuthentication";
+// static
 const char GaiaAuthFetcher::kCaptchaError[] = "CaptchaRequired";
 // static
 const char GaiaAuthFetcher::kServiceUnavailableError[] =
@@ -344,13 +346,18 @@ GoogleServiceAuthError GaiaAuthFetcher::GenerateAuthError(
       return GoogleServiceAuthError(GoogleServiceAuthError::ACCOUNT_DELETED);
     if (error == kAccountDisabledError)
       return GoogleServiceAuthError(GoogleServiceAuthError::ACCOUNT_DISABLED);
+    if (error == kBadAuthenticationError) {
+      return GoogleServiceAuthError(
+          GoogleServiceAuthError::INVALID_GAIA_CREDENTIALS);
+    }
     if (error == kServiceUnavailableError) {
       return GoogleServiceAuthError(
           GoogleServiceAuthError::SERVICE_UNAVAILABLE);
     }
 
+    LOG(WARNING) << "Incomprehensible response from Google Accounts servers.";
     return GoogleServiceAuthError(
-        GoogleServiceAuthError::INVALID_GAIA_CREDENTIALS);
+        GoogleServiceAuthError::SERVICE_UNAVAILABLE);

[John Gregg, 2010/12/01 00:58:15]

Neither one of these is natural as the default.  If we are going to change the
default now, perhaps it's an opportunity to add "UNKNOWN_ERROR".

[Chris Masone, 2010/12/01 16:51:26]

I dunno...it seems to me that what this means is we can't successfully talk to
the service, so SERVICE_UNAVAILABLE makes sense.  I don't know that using
UNKNOWN_ERROR would allow us to show a more useful error to the user in this
case.  I suppose we could add UNKNOWN_ERROR for logging purposes, or to allow
callers of this API to distinguish these cases, but conflate this error with
something like SERVICE_UNAVAILABLE for UI messaging purposes?

[John Gregg, 2010/12/02 19:02:16]

I was thinking SERVICE_UNAVAILABLE implies "try again later" where as this
incomprensible response means something is more seriously wrong, like we're
talking to a different version of the server.

But this is probably fine.

[Chris Masone, 2010/12/02 22:59:49]

We've seen this in a captive portal situation as well, so really... "try again
later" is the only thing the system can do in this case, kinda no matter what.

Given that, and the trybot run...how do you feel about the change?

   }
 
   NOTREACHED();