-
Bug
-
Resolution: Fixed
-
High
-
None
Currently, we retrieve the Locale for a web-resource request via the current user's authentication context, for example fr_FR.
This is a problem, because if web-resource url for the request contains a different Locale _en_UK then we will retrieve and then cache contents localised to the wrong Locale.
In this example we would cache the en_UK url with content fetched in fr_FR
- is detailed by
-
JRASERVER-28392 The language translation got mixed up in the dashboard after choosing a default language other than the chosen one from initialization
- Closed
-
PLUGWEB-99 Loading...
- relates to
-
JRACLOUD-37917 Upgrade to new atlassian web-resources to prevent poisoning cached i18n dependent JS resources
- Closed