Skip to content

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

Open
solracsf wants to merge 1 commit into
masterfrom
invalidateRootETag
Open

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

Conversation

@solracsf

@solracsf solracsf commented Apr 2, 2026

Copy link
Copy Markdown
Member

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

Signed-off-by: Git'Fellow <12234510+solracsf@users.noreply.github.com>
@solracsf
solracsf force-pushed the invalidateRootETag branch from 6b0943b to bba30d8 Compare July 17, 2026 10:40
@solracsf

Copy link
Copy Markdown
Member Author

Adapted to use Cache::update()

@solracsf solracsf modified the milestones: Nextcloud 34, Nextcloud 35 Jul 17, 2026
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