The HTTP requests for the data.zip of the Loot-Table Randomizer and the Crafting-Recipe Randomizer are currently using the default caching logic, provided by a user's browser.
This becomes a problem, when the data of existing versions has been altered.
Instead, the request itself should never be cached, but always be pulled fresh and then only kept in cache for the session the user is currently in.
An interceptor for the session-caching already exists, the request itself just needs to be performed with the required no-cache headers.
The HTTP requests for the data.zip of the Loot-Table Randomizer and the Crafting-Recipe Randomizer are currently using the default caching logic, provided by a user's browser. This becomes a problem, when the data of existing versions has been altered. Instead, the request itself should never be cached, but always be pulled fresh and then only kept in cache for the session the user is currently in. An interceptor for the session-caching already exists, the request itself just needs to be performed with the required no-cache headers.