CTRL ALTSCtrl Alt Solvereal-world developer knowledge
SearchJoin
Ctrl Alt Solve — Don't just ask what to do. Learn what developers experienced when they did it.

Developer experience network

Ctrl Alt Solve

Real-world experiences, production lessons, and structured discussions — knowledge that goes beyond tutorials.

Search

Explore by technology

Open an experience to follow topics you care about.

#postgres·135#queues·91#redis·91#observability·87#sre·87#opentelemetry·87#networking·78#career·78#leadership·78#debugging·78#nginx·78#nextjs·73#edge·73#auth·73#architecture·68#billing·68

Experience feed

Unread-first ranked posts for #auth

DiscoverLatestFor you
AllQuestionExperienceDiscussionComparisonCase studyLearningProblem solvingRecommendationShowcaseCareer
Experience18d ago·1 entry

broke when we moved auth to the edge

We moved session checks to the edge to cut latency on every page load. It worked in staging, then failed on preview deploys when cookies crossed domains. Clock skew between edge and origin made short-lived tokens look expired. We fixed cookie domains per environment and added skew-tolerant expiry. Median auth path dropped about 120ms, with fewer cold-start surprises. Lesson: test cookies across every environment before calling a migration done.

397 views0 likes0 comments0 bookmarks
#nextjs#auth#edge
SSumanth Rao
Read →
Experience20d ago·1 entry

broke when we moved auth to the edge

We moved session checks to the edge to cut latency on every page load. It worked in staging, then failed on preview deploys when cookies crossed domains. Clock skew between edge and origin made short-lived tokens look expired. We fixed cookie domains per environment and added skew-tolerant expiry. Median auth path dropped about 120ms, with fewer cold-start surprises. Lesson: test cookies across every environment before calling a migration done.

412 views0 likes0 comments0 bookmarks
#nextjs#auth#edge
MMarcus Webb
Read →
Experience18d ago·1 entry

broke when we moved auth to the edge

We moved session checks to the edge to cut latency on every page load. It worked in staging, then failed on preview deploys when cookies crossed domains. Clock skew between edge and origin made short-lived tokens look expired. We fixed cookie domains per environment and added skew-tolerant expiry. Median auth path dropped about 120ms, with fewer cold-start surprises. Lesson: test cookies across every environment before calling a migration done.

387 views0 likes0 comments0 bookmarks
#nextjs#auth#edge
JJhansi Rani
Read →
ExperienceSep 7, 2026·1 entry

broke when we moved auth to the edge

We moved session checks to the edge to cut latency on every page load. It worked in staging, then failed on preview deploys when cookies crossed domains. Clock skew between edge and origin made short-lived tokens look expired. We fixed cookie domains per environment and added skew-tolerant expiry. Median auth path dropped about 120ms, with fewer cold-start surprises. Lesson: test cookies across every environment before calling a migration done.

403 views0 likes0 comments0 bookmarks
#nextjs#auth#edge
KKavitha Rani
Read →
Experience28d ago·1 entry

broke when we moved auth to the edge

We moved session checks to the edge to cut latency on every page load. It worked in staging, then failed on preview deploys when cookies crossed domains. Clock skew between edge and origin made short-lived tokens look expired. We fixed cookie domains per environment and added skew-tolerant expiry. Median auth path dropped about 120ms, with fewer cold-start surprises. Lesson: test cookies across every environment before calling a migration done.

396 views0 likes0 comments0 bookmarks
#nextjs#auth#edge
HHarish Reddy
Read →
ExperienceSep 1, 2026·1 entry

broke when we moved auth to the edge

We moved session checks to the edge to cut latency on every page load. It worked in staging, then failed on preview deploys when cookies crossed domains. Clock skew between edge and origin made short-lived tokens look expired. We fixed cookie domains per environment and added skew-tolerant expiry. Median auth path dropped about 120ms, with fewer cold-start surprises. Lesson: test cookies across every environment before calling a migration done.

397 views0 likes0 comments0 bookmarks
#nextjs#auth#edge
LLavanya Devi
Read →
Experience18d ago·1 entry

broke when we moved auth to the edge

We moved session checks to the edge to cut latency on every page load. It worked in staging, then failed on preview deploys when cookies crossed domains. Clock skew between edge and origin made short-lived tokens look expired. We fixed cookie domains per environment and added skew-tolerant expiry. Median auth path dropped about 120ms, with fewer cold-start surprises. Lesson: test cookies across every environment before calling a migration done.

334 views0 likes0 comments0 bookmarks
#nextjs#auth#edge
AAnitha Selvam
Read →
ExperienceAug 24, 2026·1 entry

broke when we moved auth to the edge

We moved session checks to the edge to cut latency on every page load. It worked in staging, then failed on preview deploys when cookies crossed domains. Clock skew between edge and origin made short-lived tokens look expired. We fixed cookie domains per environment and added skew-tolerant expiry. Median auth path dropped about 120ms, with fewer cold-start surprises. Lesson: test cookies across every environment before calling a migration done.

389 views0 likes0 comments0 bookmarks
#nextjs#auth#edge
SSaurabh Mishra
Read →
Experience14d ago·1 entry

broke when we moved auth to the edge

We moved session checks to the edge to cut latency on every page load. It worked in staging, then failed on preview deploys when cookies crossed domains. Clock skew between edge and origin made short-lived tokens look expired. We fixed cookie domains per environment and added skew-tolerant expiry. Median auth path dropped about 120ms, with fewer cold-start surprises. Lesson: test cookies across every environment before calling a migration done.

256 views0 likes0 comments0 bookmarks
#nextjs#auth#edge
MMadhavi Latha
Read →
Experience26d ago·1 entry

broke when we moved auth to the edge

We moved session checks to the edge to cut latency on every page load. It worked in staging, then failed on preview deploys when cookies crossed domains. Clock skew between edge and origin made short-lived tokens look expired. We fixed cookie domains per environment and added skew-tolerant expiry. Median auth path dropped about 120ms, with fewer cold-start surprises. Lesson: test cookies across every environment before calling a migration done.

371 views0 likes0 comments0 bookmarks
#nextjs#auth#edge
MManasa Priya
Read →
Experience16d ago·1 entry

broke when we moved auth to the edge

We moved session checks to the edge to cut latency on every page load. It worked in staging, then failed on preview deploys when cookies crossed domains. Clock skew between edge and origin made short-lived tokens look expired. We fixed cookie domains per environment and added skew-tolerant expiry. Median auth path dropped about 120ms, with fewer cold-start surprises. Lesson: test cookies across every environment before calling a migration done.

287 views0 likes0 comments0 bookmarks
#nextjs#auth#edge
NNaveen Kumar
Read →
ExperienceAug 20, 2026·1 entry

broke when we moved auth to the edge

We moved session checks to the edge to cut latency on every page load. It worked in staging, then failed on preview deploys when cookies crossed domains. Clock skew between edge and origin made short-lived tokens look expired. We fixed cookie domains per environment and added skew-tolerant expiry. Median auth path dropped about 120ms, with fewer cold-start surprises. Lesson: test cookies across every environment before calling a migration done.

361 views0 likes0 comments0 bookmarks
#nextjs#auth#edge
NNisha Verma
Read →