Don't relaunch app for non-auth errors.

remoting/webapp/crd/js/remoting.js

Index: remoting/webapp/crd/js/remoting.js
diff --git a/remoting/webapp/crd/js/remoting.js b/remoting/webapp/crd/js/remoting.js
index bc23d7ce367509de612a192092329144717c93cb..d160add522b17c99e669f3bfc5b5434e9f16d6e2 100644
--- a/remoting/webapp/crd/js/remoting.js
+++ b/remoting/webapp/crd/js/remoting.js
@@ -182,7 +182,7 @@ remoting.showErrorMessage = function(error) {
       document.getElementById('token-refresh-error-message'),
       error);
   var auth_failed = (error == remoting.Error.AUTHENTICATION_FAILED);
-  if (base.isAppsV2()) {

[kelvinp, 2015/03/04 21:06:56]

I think another problem is that at error.js

https://code.google.com/p/chromium/codesearch#chromium/src/remoting/webapp/cr...

We handle all unknown HTTP error as AUTHENTICATION_FAILED.
Would that needs to be addressed as well?

[Jamie, 2015/03/04 23:11:19]

Kelvin and I discussed in person, and felt that since unexpected HTTP response
codes are (hopefully) rare, we can ignore that problem for the time being.

+  if (auth_failed && base.isAppsV2()) {
     remoting.handleAuthFailureAndRelaunch();
   } else {
     document.getElementById('token-refresh-auth-failed').hidden = !auth_failed;