[Bug]: Regression: Modtimes no longer updated when uploading to a shared folder through webdav

[kramlie]

⚠️ 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

When using a tool like rclone to sync files with a password protected shared folder over webdav, it is unable to update the modification times of the files it uploads. This causes it to get confused when it later checks the server for updates.

This is a regression, it used to work in a previous version. Unfortunately I can't tell you exactly which one, since I'm using a hosted server which I have limited control over. The server being used now is version 32.

Steps to reproduce

1. Create a folder test on the nextcloud server and share it via a link. Enable a password and full write access.
2. Install the latest rclone command line tool.
3. Execute rclone config, and follow the prompts.
   • Set the type to webdav.
   • Set the link to https://<SERVER>/public.php/webdav.
   • Set the user to the last element of the share link.
   • Set vendor to owncloud, not nextcloud (this is to avoid an issue where rclone does not accept a share URL; it is however not related to the problem, since this worked previously).
   • Make a note of the name you gave the remote.
4. Create a test folder locally.
5. Create a test file like so: echo test > test/testfile
6. Set the modification time to some time in the past, for example like this: touch -r /etc/motd test/testfile.
7. Execute this: rclone sync test/ <REMOTENAME>:/test/
8. Execute this: rclone lsl <REMOTENAME>:/test/

Expected behavior

Expected behavior is that the listed file has the same modification time as the local /etc/motd file, used in the touch command above. Instead, the file has the current time.

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?

Upgraded to a MAJOR version (ex. 31 to 32)

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

I don't know much about the server environment unfortunately, since it is hosted. I only know that it's server version 32.