[Bug]: Nextcloud Client ignores maxChunkSize for bulk uploads

[matthesvoss]

⚠️ Before submitting, please verify the following: ⚠️

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

Bug description

I am using a cloudflare tunnel so the request body size is limited to 100MB. When I start the sync, after a while the client tries to do a bulk upload to /remote.php/dav/bulk exceeding the 100MB limit and resulting in a "413 Request Entity Too Large" error halting the sync. I tried setting the maxChunkSize in the client config to as low as 50000000 but it does not change the behaviour. When I disable bulk uploads in the server config using 'bulkupload.enabled' => false, everything is working fine.

20250306_0506_nextcloud.log

Steps to reproduce

1. Setup nextcloud behind a cloudflare tunnel
2. Set the maxChunkSize in the client config to a value below 100000000
3. Sync a large amount of files
4. Observe a "413 Request Entity Too Large" error in the client logs after a while

Expected behavior

The maxChunkSize should also be used by bulk uploads. Ideally it should use the files.chunked_upload.max_size setting from the server.

Which files are affected by this bug

20250306_0506_nextcloud.log

Operating system

Windows

Which version of the operating system you are running.

Windows 11

Package

Official Windows MSI

Nextcloud Server version

31.0.0

Nextcloud Desktop Client version

3.15.3

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

Updated to a major version (ex. 3.3.6 to 3.4.0)

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

Are you using an external user-backend?

• Default internal user-backend
• LDAP/ Active Directory
• SSO - SAML
• Other

Nextcloud Server logs

Additional info

No response