So, apparently UiPath Forum is generating very large cookies on Google Chrome, like the image below:
Is that normal? I don`t even access here very often. In another machine of mine, where I use the forum more frequently, it was already on 5gb on size.
bcorrea
(Bruno Correa)
June 17, 2020, 1:35pm
2
mine is 2.1GB, indeed quite big… @Pablito do you know why this is so big?
Pablito
(Pawel Wozniak)
June 18, 2020, 2:28pm
3
Hi Guys,
Thanks for letting us know. I’ve checked this case with our platform provider. Seems that the problem is known and occurs only on the Android OS and the Chrome Browser. In fact those cookie sizes are fake and they are working on solution for that.
More info:
opened 07:54AM - 16 Sep 19 UTC
closed 03:11PM - 17 Sep 19 UTC
We use:
```
workbox.routing.registerRoute(
new RegExp('.*?'), // Matches … all, GET is implicit
new workbox.strategies.NetworkFirst({ // This will only use the cache when a network request fails
cacheName: "discourse-1",
plugins: [
new workbox.expiration.Plugin({
maxAgeSeconds: 7* 24 * 60 * 60, // 7 days
maxEntries: 500,
purgeOnQuotaError: true, // safe to automatically delete if exceeding the available storage
}),
],
})
);
```
To cache on Android so Discourse (eg: meta.discourse.org) can work offline.
Users started reporting that our app is reporting enormous data usage per:

Our analysis of such a device is that there is no such storage going on and instead its due to opaque request caching blowing the perceived size. https://developers.google.com/web/tools/chrome-devtools/progressive-web-apps#opaque-responses. For example we have 157 tiny CSS files that are coming in as opaque.
Can workbox workaround this issue by using some sort of different container for caching?
Are we misusing workbox?
Should we report something to android?
4 Likes