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'm not entirely certain about this, but since I have a hunch this is causing the issues I'm seeing and the consequences might be serious, I want to report it sooner rather than later.
Looking at issue #89 and PR #90 where collected CSS and JS leaks from one template render to another, I suspect the same happens to Catalog._tmpl_globals, which has exactly the same usage pattern as collected_css and collected_js.
If one uses the template globals to pass e.g. the request object to components, this can cause serious issues, where templates are rendered based on the request objects belonging to different users.
The text was updated successfully, but these errors were encountered:
I'm not entirely certain about this, but since I have a hunch this is causing the issues I'm seeing and the consequences might be serious, I want to report it sooner rather than later.
Looking at issue #89 and PR #90 where collected CSS and JS leaks from one template render to another, I suspect the same happens to
Catalog._tmpl_globals
, which has exactly the same usage pattern ascollected_css
andcollected_js
.If one uses the template globals to pass e.g. the request object to components, this can cause serious issues, where templates are rendered based on the request objects belonging to different users.
The text was updated successfully, but these errors were encountered: