You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This would be a handy feature. But it will still require web pages (making use of neo viewer) to be kept track of and updated (with this option) when a particular file is changed. At the time of creating the webpage, authors might not anticipate changes and would prefer to make use of the caching feature for performance reasons. And eventually they are likely to forget the caching aspect. It might be useful to consider caching to be disabled as default, or have some minimal checks such as if the file size has changed (via HTTP HEAD method; not foolproof but some basic check) .
I believe we can make use of "Content-Length" and "Last-Modified" to compare if the cached file is same as the file currently at the target URL, as some basic check (which should probably suffice for our purposes).
for example, suppose the file at a given URL is exchanged for another with the same name
The text was updated successfully, but these errors were encountered: