From a5c3108a90bbefb53319ae89f9d5ac2e067fb262 Mon Sep 17 00:00:00 2001 From: Matchu Date: Thu, 27 May 2021 17:29:06 -0700 Subject: [PATCH] Whoops, fix outfitImage caching bug I was accidentally serving images _without_ `updatedAt` with the long-term cache headers, but only in prod, not in dev I think this is probably because I made a mistake in my Vercel route config, by including an `$updatedAt` parameter that doesn't actually exist in this case. I'm guessing the Vercel dev server has different behavior for my mistake than the prod server. I'm guessing the dev server makes it an empty string, and the prod server makes it the literal string `$updatedAt`. Oops! I hope this fixes it! --- vercel.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/vercel.json b/vercel.json index 2ad49261..1b624f9c 100644 --- a/vercel.json +++ b/vercel.json @@ -2,7 +2,7 @@ "routes": [ { "src": "/outfits/(?[^/]+)/(?150|300|600).png", - "dest": "/api/outfitImage.js?size=$size&id=$id&updatedAt=$updatedAt" + "dest": "/api/outfitImage.js?size=$size&id=$id" }, { "src": "/outfits/(?[^/]+)/v/(?[^/]+)/(?150|300|600).png",