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
When Nginx has the default settings enabled, which treats caching normally, often when opening an action or other pages the browser is opening cached data.
If nginx is set with cache control headers "no-store" and "no-cache", the webui opens the most current data.
Deployment of st2 and st2web is very stock-standard config.
This issue can be replicated by simply modifying a simple action in the webui, saving it, closing that browser tab, then opening the action again in the webui, and the old cached data is loaded, not the most recent saved version.
Tested on 5 different browsers (edge, chrome, firefox, opera, brave) across two different OS's (Ubuntu, Win11) and two different methods of connecting (local network and via internet).. Issue persists across all..
Set the abovementioned cache control headers in the nginx config, and the issue is resolved.
The text was updated successfully, but these errors were encountered:
When Nginx has the default settings enabled, which treats caching normally, often when opening an action or other pages the browser is opening cached data.
If nginx is set with cache control headers "no-store" and "no-cache", the webui opens the most current data.
Deployment of st2 and st2web is very stock-standard config.
This issue can be replicated by simply modifying a simple action in the webui, saving it, closing that browser tab, then opening the action again in the webui, and the old cached data is loaded, not the most recent saved version.
Tested on 5 different browsers (edge, chrome, firefox, opera, brave) across two different OS's (Ubuntu, Win11) and two different methods of connecting (local network and via internet).. Issue persists across all..
Set the abovementioned cache control headers in the nginx config, and the issue is resolved.
The text was updated successfully, but these errors were encountered: