Safari 26.0.1: __prerender_bypass cookie present in production #14074
Replies: 1 comment
-
Well, the issue is rather stupid. Cleaning all the cache for the website solved everything. However, where did the production website get these cookies - a mystery that will be never solved. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
After updating to macOS 26 and thus migrating to Safari 26.0.1, Next/Payload website hosted on Vercel started to load extremely slowly (like 4.5 seconds). After short check, I've found
__prerender_bypass
and__next_preview_data
cookies in requestx-vercel-cache: BYPASS
andCache-Control: private, no-cache, no-store, max-age=0, must-revalidate
in response.At the same time, no such cookies and in general all good on:
Google PageSpeed insights shows 97 mobile and 100 desktop performance check.
My question to community: has anyone ever faced something similar? If yes, how have you mitigated that in an intelligent way?
Happy new macOS release! :'(
P.S. Meanwhile, I'm going YOLO mode and updating to iOS 26 Developer Beta to see if the behaviour is also present there. I'll update the post with new findings soon.
Beta Was this translation helpful? Give feedback.
All reactions