[Bug]: WebDAV SEARCH pagination always reports total as 100 and does not return next page token after second request

[marinofaggiana]

⚠️ This issue respects the following points: ⚠️

• This is a bug, not a question or a configuration/webserver/proxy issue.
• This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
• Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
• I agree to follow Nextcloud's Code of Conduct.

Bug description

I’m seeing an issue with WebDAV SEARCH pagination.

When using SEARCH with pagination enabled, the response header x-nc-paginate-total always returns 100, even when the actual number of matching items is clearly higher.

The first paginated request works and returns a pagination token.
However, when requesting the second page, the server still returns:

x-nc-paginate: true

but no longer returns a pagination token for the next page.

This makes it impossible for the client to continue loading the remaining search results, even though the server explicitly indicates that pagination is still active.

Steps to reproduce

Send a webDAV
<d:searchrequest xmlns:d="DAV:" xmlns:oc="http://owncloud.org/ns\" xmlns:nc="http://nextcloud.org/ns\">
with the x-nc-paginate: true

Expected behavior

When there are more than 100 matching items:
x-nc-paginate-total
should return the real total number of matching items, or at least a correct value higher than the current page size.

x-nc-paginate: true
indicates that more results are available should include a valid next-page token.

Nextcloud Server version

32

Operating system

None

PHP engine version

None

Web server

None

Database engine version

None

Is this bug present after an update or on a fresh install?

None

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?

• Default user-backend (database)
• LDAP/ Active Directory
• SSO - SAML
• Other

Configuration report

List of activated Apps

Nextcloud Signing status

Nextcloud Logs

Additional info

No response