From 0cabd263444e0b0057ad92ba0e3e36cf2fbf93ba Mon Sep 17 00:00:00 2001
From: Jackson Harper <jacksonh@gmail.com>
Date: Thu, 26 May 2022 16:04:21 -0700
Subject: [PATCH] Dont send the normalized URL to the content-fetch service

URLs need to be sent to contentFetch exactly as they
were received, this is because many apps will use signed URLs
for PDFs being served from GCP or AWS. A signed URL needs to
keep all its query params in the same order to validate.
---
 packages/api/src/services/create_page_save_request.ts | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/packages/api/src/services/create_page_save_request.ts b/packages/api/src/services/create_page_save_request.ts
index ca8c0c357..60a7e5672 100644
--- a/packages/api/src/services/create_page_save_request.ts
+++ b/packages/api/src/services/create_page_save_request.ts
@@ -83,13 +83,14 @@ export const createPageSaveRequest = async (
   priority = priority || (await getPriorityByRateLimit(userId))
 
   // look for existing page
-  url = normalizeUrl(url, {
+  const normalizedUrl = normalizeUrl(url, {
     stripHash: true,
     stripWWW: false,
   })
+
   let page = await getPageByParam({
     userId,
-    url,
+    url: normalizedUrl,
   })
   if (page) {
     console.log('Page already exists', page)