3 ms·

>Firefox, for example has `about:cache` May I ask whats the equivalent for it in Chrome as majority of users are on Chrome for me. >> as my enterprise I want

>Firefox, for example has `about:cache` May I ask whats the equivalent for it in Chrome as majority of users are on Chrome for me. >> as my enterprise I want to push objects to my employee's cache using an API Well, theoretically you can do it using Service Workers today (https://developers.google.com/web/ilt/pwa/caching-files-with-service-worker https://developers.google.com/web/ilt/pwa/caching-files-with...) but I want to do it in a automated way so that I minimize the thundering herd when everyone comes tomorrow on Monday morning apart from enabling an offline experience (users in some countries have crappy connections so asynchronously pushing it is a way to solve it) >Combine it with some basic packet capturing of new TLS connections and I could push arbitrary JS that did event capturing on all the sites that employees visited. Hmm..I need more on this but the idea is they are SRI checked and come from a supply source thats trusted (but I get your drift on solar winds kind of lateral attack), but if I am right then what you say can even be done with the service worker API I mentioned above

paranoidrobot 4y ago
> May I ask whats the equivalent for it in Chrome as majority of users are on Chrome for me. I think for Chrome it's under devtools: https://developer.chrome.com/docs/devtools/storage/cache/ https://developer.chrome.com/docs/devtools/storage/cache/ > what you say can even be done with the service worker API I mentioned above Well no, because service worker API is going to be subject to the same security policies as any other site. If I understand what it is you're asking for, you want the Web-equivalent of doing something like doing overnight pushes of software updates to the enterprise. I don't know your environment, but you might be better off solving this by pushing large cachable things to edge caches closer to your users. If they're on the public internet, then caching resources out of a public CDN might do the trick. If they're on private networks in offices, then perhaps deploying something to those offices to serve local cache might work. You don't necessarily need networking magic to make this happen - a service that can locate your users, and then issue HTTP redirects to a local cache server could possibly do it. eg: call https://cache-main.example.com/some/resource.js https://cache-main.example.com/some/resource.js, the server does a geo lookup on my IP, and issues a 301 to https://cache-some-remote-location.example.com/some/resource.js https://cache-some-remote-location.example.com/some/resource... Trying to automate things like updating a user's cache directly in their browser seems like a major pain. How do you handle them not being logged in/sleeping/having multiple browser profiles/etc etc etc.

paranoidrobot 4y ago

> May I ask whats the equivalent for it in Chrome as majority of users are on Chrome for me. I think for Chrome it's under devtools: https://developer.chrome.com/docs/devtools/storage/cache/ https://developer.chrome.com/docs/devtools/storage/cache/ > what you say can even be done with the service worker API I mentioned above Well no, because service worker API is going to be subject to the same security policies as any other site. If I understand what it is you're asking for, you want the Web-equivalent of doing something like doing overnight pushes of software updates to the enterprise. I don't know your environment, but you might be better off solving this by pushing large cachable things to edge caches closer to your users. If they're on the public internet, then caching resources out of a public CDN might do the trick. If they're on private networks in offices, then perhaps deploying something to those offices to serve local cache might work. You don't necessarily need networking magic to make this happen - a service that can locate your users, and then issue HTTP redirects to a local cache server could possibly do it. eg: call https://cache-main.example.com/some/resource.js https://cache-main.example.com/some/resource.js, the server does a geo lookup on my IP, and issues a 301 to https://cache-some-remote-location.example.com/some/resource.js https://cache-some-remote-location.example.com/some/resource... Trying to automate things like updating a user's cache directly in their browser seems like a major pain. How do you handle them not being logged in/sleeping/having multiple browser profiles/etc etc etc.