Suggest to add to the settings the new option (switch): "Cache-Control"
When ON: prohibits refresh the web-page when you click on the "Back" button (ignore the "no-store/no-cache" instructions and loads content from cache);
When OFF: regular behavior;
-------------------------------------------
In the current build I manually edit files chrome.dll/chrome_child.dll to achieve effect.
Are you familiar with JavaScript?
This should better be implemented by chrome extension.
You can filter network response headers and remove Cache-Control: no-cache
I tried the ModHeader extension, but don`t achieve the result
I set in Profile1:
May be I need another settings? (what exactly?)
And I tried set:
No avail
(05-27-2019, 05:03 PM)Zebra Wrote: [ -> ]I tried the ModHeader extension, but don`t achieve the result
I set in Profile1:
May be I need another settings? (what exactly?)
And I tried set:
No avail
Your usage should be working normally.
But seems this extension doesn't work in some websites.
Besides "Cache-Control", there are other headers used for cache validation.
So the situation may be complicated.
Maybe you need offline mode?
https://www.wikihow.com/Work-Offline-on-Chrome
https://chrome.google.com/webstore/detai...bodajcojda
I tried all available "headers" extensions from ChromeStore -- no one can manage
Response Headers values
The flag chrome://flags/#show-saved-copy (and extension "Work Offline" or something like that) can`t help due to the fact that the Response Headers has the cache-control: no-store --- the Cent don`t save content to the cache in accordance with the "no-store".
I think there is only one good way: embed a function in the browser code to ignore the Cache-Control response header.
(05-28-2019, 06:21 PM)Zebra Wrote: [ -> ]I tried all available "headers" extensions from ChromeStore -- no one can manage Response Headers values
The flag chrome://flags/#show-saved-copy (and extension "Work Offline" or something like that) can`t help due to the fact that the Response Headers has the cache-control: no-store --- the Cent don`t save content to the cache in accordance with the "no-store".
I think there is only one good way: embed a function in the browser code to ignore the Cache-Control response header.
May I know why you need this feature?
To save bandwidth?