-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Downloading images stored in cache not working in Firefox 123 #91
Comments
Thanks for the reply. Hopefully Mozilla will eventually implement a workaround for addons (although I won't be holding my breath waiting for it). |
Found a method to download from cache, released in addon v4.4.0. Still requires the cache workaround. |
The cache fix works like a dream. Thank-you so much for following up on this. Where I live (Australia) a lot of city homes have their broadband Internet delivered via 50+ year old copper wire, so not having to download large images from galleries twice can make a very big difference. With my Firefox cache capacity size increased to 2GB from the default of 256MB, Tab Image Saver enables me to easily save 10-20 image tabs in one go without re-downloading, even if the pictures are very big (over 25MB). |
I have been using this addon for several months without any issues, however the recent upgrade of Firefox to version 123.0 seems to prevent Tab Image Saver from reading images from the cache, even with privacy.partition.network_state set to false. This means every image has to be downloaded twice - once to view in the browser and once to save with Tab Image Saver. Could this new issue possibly be related to this security fix listed on Firefox 123.0, See All New Features, Updates and Fixes?
CVE-2024-1554: fetch could be used to effect cache poisoning
Reporter
scarlet
Impact
moderate
Description
The fetch() API and navigation incorrectly shared the same cache, as the cache key did not include the optional headers fetch() may contain. Under the correct circumstances, an attacker may have been able to poison the local browser cache by priming it with a fetch() response controlled by the additional headers. Upon navigation to the same URL, the user would see the cached response instead of the expected response.
References
The text was updated successfully, but these errors were encountered: