Skip to content

fix(quota): Invalidate root ETag on quota change#4539

Open
solracsf wants to merge 1 commit intomasterfrom
invalidateRootETag
Open

fix(quota): Invalidate root ETag on quota change#4539
solracsf wants to merge 1 commit intomasterfrom
invalidateRootETag

Conversation

@solracsf
Copy link
Copy Markdown
Member

@solracsf solracsf commented Apr 2, 2026

When the quota of a team folder changes, desktop clients continued to receive the stale quota-available-bytes value on subsequent PROPFINDs until the etag of the folder root changed. This fix invalidates the root etag immediately after the quota is updated, without requiring a mounted storage or an active user session.

This forces every desktop client to issue a fresh PROPFIND on the next sync cycle, at which point the DAV layer computes and returns the updated quota-available-bytes value.

Server side: nextcloud/server#59398
Needed for nextcloud/desktop#4580

@solracsf solracsf force-pushed the invalidateRootETag branch from 362319d to 08a628e Compare April 2, 2026 08:46
Signed-off-by: Git'Fellow <12234510+solracsf@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3. to review Items that need to be reviewed enhancement feature: quota Items realted to the quota feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant