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
I am using InMemoryBackend for FastAPI paths. It seems like different sources have different caches, i.e. requests issued by the same browser are correctly cached even if cache_status_header is MISS (response time is zero and fastapi does not log). However, if the request is issued by another browser window, cache does not work and the new request is fully processed. Is there any additional setting to fix this behavior? Am I missing something?
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
-
I am using InMemoryBackend for FastAPI paths. It seems like different sources have different caches, i.e. requests issued by the same browser are correctly cached even if
cache_status_headeris MISS (response time is zero and fastapi does not log). However, if the request is issued by another browser window, cache does not work and the new request is fully processed. Is there any additional setting to fix this behavior? Am I missing something?Beta Was this translation helpful? Give feedback.
All reactions