Handle bad-token errors

401 errors now trigger a logout, so a bad token will generate one error then be removed.
prismic-archive · Jun 10, 2014 · f724a6c · f724a6c
1 parent 658c45a
commit f724a6c
Show file tree

Hide file tree

Showing 2 changed files with 15 additions and 3 deletions.
diff --git a/src/baked.js b/src/baked.js
@@ -9,8 +9,8 @@ var Q = require("q");
   function getAPI(conf) {
     var deferred = Q.defer();
     Prismic.Api(conf.api, function(err, api) {
-      if(err) {
-        conf.logger.error("Error while fetching Api at %s", conf.api, err);
+      if (err) {
+        err.url = conf.api;
         deferred.reject(err);
       }
       else deferred.resolve(api);

diff --git a/src/browser.js b/src/browser.js
@@ -224,7 +224,19 @@ var LocalRouter = require("./local_router");
         var infos =
           window.routerInfosForFile ||
           localRouter.findInfosFromHref(location.pathname);
-        return loadPage(localRouter, infos);
+        return loadPage(localRouter, infos)
+          .catch(function (err) {
+            if (accessToken && /^Unexpected status code \[401\]/.test(err.message)) {
+              console.warn("Received 401 (Unauthorized) error:");
+              console.error(err.stack);
+              console.warn("Retry without access_token");
+              sessionStorage.removeItem('ACCESS_TOKEN');
+              accessToken = undefined;
+              ref = undefined;
+              return loadPage(localRouter, infos);
+            }
+            throw err;
+          });
       })
       .done();
   }