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
For routes that requires authentication, Nginx should have separate caches for each user.
Adding res.set('Cache-Control', 'private') to the routes does not work (cache is not getting hit for same user). Also, adding cache policies in application code is rather ugly.
Is there a more elegant way for Nginx caching and passportjs to work seamlessly?
This discussion was converted from issue #700 on June 19, 2021 00:18.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
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.
-
For routes that requires authentication, Nginx should have separate caches for each user.
Adding
res.set('Cache-Control', 'private')to the routes does not work (cache is not getting hit for same user). Also, adding cache policies in application code is rather ugly.Is there a more elegant way for Nginx caching and passportjs to work seamlessly?
Beta Was this translation helpful? Give feedback.
All reactions