HI Ashuman,
Thank you for looking into this. I’d say the best way is to have the site open without any activity for a while until session becomes stale and browse it again - unsure how many exact minutes on vercel.
Digging it a bit dipper in browser console, I see below static artifact structure (not my code structure/folder - what is created after react site deployment by vercel as a static media) and issue is on files in media folder. They get 403 forbidden when the user is inactive for whatever duration Vercel considers session is inactive.
Specific error on browser is "Failed to load resource: the server responded with a status of 403 ()”. On the surface level, it appears some sort of security feature from Vercel blocking image files in media folder no longer accessible to browser if vercel thinks the user session is no longer active? But for public website this is really bad, users should be able to have the webpage open as long as they need to whether they are active or not without all the images become broken on the site. This is why I am wondering if vercel is right solution for public/production websites.
Am I missing some settings for deployment to prevent this? I spent many hours googling and reading your doc site and have not found anything about this issue.
top
L www.bltz.ai
L static
L css
L js
L media
