Replies: 1 comment
-
|
Deployed nginx as a reverse proxy sidecar that enforces cache-control policies: critical files (HTML, service workers, manifests) are never cached while static assets with hashed filenames cache aggressively. This seems to solve the stale version problem where browser-cached service workers would continue serving old application code after updates. |
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.
Uh oh!
There was an error while loading. Please reload this page.
-
I’m having issues when updating Open WebUI where chats will hang indefinitely. A hard refresh seems to fix the issue.
In going from 0.6.2x to 0.6.30, all users were required to hard refresh the Open WebUI page or chats would hang.
In going from 0.6.30 to 0.6.36, the same issue occurred.
This was reproducible:
I’m running this on 4 instances of ECS with redis and postgres. Routing is handled by an ALB / sticky sessions, conditional routing. Requests go to litellm proxy - doesn’t seem to be issues there. I’ve tried removing redis and scaling down to 1 running instance and the issue persisted. I could not find any errors in Open WebUI backend or in Dev Tools on the front end.
Anyone else have this issue or have ideas on how to fix?
Beta Was this translation helpful? Give feedback.
All reactions