public/obsidian-livesync
1
0 Fork 0
mirror of https://github.com/vrtmrz/obsidian-livesync.git synced 2026-11-05 07:48:18 +00:00
Code Issues Packages Projects Releases Wiki Activity

Document the legacy URL behaviour of cache compatibility

Browse Source
This commit is contained in:
vorotamoroz committed 2026-11-03 01:19:07 +00:00
1 parent 667d6bed1f
commit 8c51d66adf
1 file changed
+2
Download Patch File Download Diff File Expand all files Collapse all files
docs/settings.md
+2
View File
@@ -1100,6 +1100,8 @@ If this option is enabled, PouchDB will hold the connection open for 60 seconds,
Setting key: useCouchDBCacheControlHeadersOnly Setting key: useCouchDBCacheControlHeadersOnly
Remove the query parameter used to invalidate cached responses (the same URL behaviour as in 1.0.44 and earlier).
Disabled by default. Encrypted CouchDB reads normally use a cache query parameter derived from the plug-in startup time and current Security Seed, and revalidate cached responses. This separates responses from before a remote Rebuild even when document revisions remain unchanged. Disabled by default. Encrypted CouchDB reads normally use a cache query parameter derived from the plug-in startup time and current Security Seed, and revalidate cached responses. This separates responses from before a remote Rebuild even when document revisions remain unchanged.
Enable this only if your server or proxy rejects that additional query parameter. Requests then retain their original URLs and use `no-store` with revalidation headers. Some native caches can still reuse older encrypted responses in this mode, so decryption failures after a remote Rebuild may recur. Seed refresh before replication remains active in both modes. Changing this setting does not require a database rebuild. Enable this only if your server or proxy rejects that additional query parameter. Requests then retain their original URLs and use `no-store` with revalidation headers. Some native caches can still reuse older encrypted responses in this mode, so decryption failures after a remote Rebuild may recur. Seed refresh before replication remains active in both modes. Changing this setting does not require a database rebuild.