You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How did you implement this with JWT-protected APIs?
Next.js hashes the entire request to create the cache key.
As a result, on every auth token refresh (Authorization: Bearer …), a new cache key is generated with a new redis entry, leading to duplicate redis entries.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
How did you implement this with JWT-protected APIs?
Next.js hashes the entire request to create the cache key.
As a result, on every auth token refresh
(Authorization: Bearer …), a new cache key is generated with a new redis entry, leading to duplicate redis entries.Beta Was this translation helpful? Give feedback.
All reactions