fix(scheduler-utils): only cache origin in Location header when follo…

…wing redirects #454
permaweb · Feb 12, 2024 · c5893d0 · c5893d0
1 parent 7bb32b9
commit c5893d0
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/scheduler-utils/src/client/scheduler.js b/scheduler-utils/src/client/scheduler.js
@@ -3,7 +3,7 @@ export function checkForRedirectWith ({ fetch }) {
     const response = await fetch(`${url}?process-id=${process}`, { method: 'GET', redirect: 'manual' })
     // In an HTTP redirect the Location header is the new url
     if ([301, 302, 307, 308].includes(response.status)) {
-      return response.headers.get('Location')
+      return new URL(response.headers.get('Location')).origin
     }
     return url
   }

diff --git a/scheduler-utils/src/client/scheduler.test.js b/scheduler-utils/src/client/scheduler.test.js
@@ -8,7 +8,7 @@ const mockFetch = (url, options) => {
       status: 302,
       headers: {
         get: (header) => {
-          if (header === 'Location') return 'http://newlocation.com'
+          if (header === 'Location') return 'http://newlocation.com?process-id=123'
         }
       }
     })