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
What can be improved?
KeePassium downloads the database file via WebDAV every time the app (or inapp overlay) is opened.
The solution you'd like
The WebDav server provides a precise timestamp of the last file change. Hence, KeePassium can use this timestamp to download the file only if the WebDAV server's timestamp is newer than the last synced one.
Alternatives you've considered
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered:
This would only work on direct sync connections (timestamps from the Files app are often unreliable)
…and deleted it.
Even if this caching is limited to direct connections, it is worth implementing and having in the queue. Let me just generalize it from WebDAV :)
keepassium
changed the title
WebDAV: Download database file only on if file has changed since last sync
Download database file only if it has changed since last sync
Jul 5, 2024
If you keep the DB loaded in KeePassium, whenever you activate the app it will check whether the remote database has changed — and prompt you to reload, if so.
I understand this is different from your request (using a cache file instead of downloading the database at all), but this is the closes we'll get to it for the nearest future. Now KeePassium uses the remote database as a singular source of truth, and this will be so until we implement database merging. Then things will need to get a bit more flexible :)
What can be improved?
KeePassium downloads the database file via WebDAV every time the app (or inapp overlay) is opened.
The solution you'd like
The WebDav server provides a precise timestamp of the last file change. Hence, KeePassium can use this timestamp to download the file only if the WebDAV server's timestamp is newer than the last synced one.
Alternatives you've considered
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: