nextcloud / nextcloud/server

[Bug]: Error while synchronizing if ends with an `x`

Open
#44,842 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage 27-feedback bug feature: dav hotspot: filename handling
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

⚠️ This issue respects the following points: ⚠️
Bug description

When synchronizing to the Nextcloud server, directories with a special syntax are not taken into account:
There are several subdirectories in the directory with a "lastname,firstname ()" naming scheme. Every time the first name ends with "x", the synchronization stops with the error message "forbidden..."
If I replace the x with another character or add another character, the synchronization works.

Steps to reproduce
  1. Rename a Subdirectory on a Client (Windows 11) to "lastname,firstnamex ()" - so that the firstname ends with x
    2.syncronize with the Server
    3.synchronization stops with the error message "forbidden..."
Expected behavior

the subdirectory will be ignored

Installation method

Community Web installer on a VPS or web space

Nextcloud Server version

27

Operating system

Other

PHP engine version

PHP 8.0

Web server

Apache (supported)

Database engine version

MySQL

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

No response

List of activated Apps

No response

Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is identified. Start by reproducing the failure with a Windows 11 client using a directory named "lastname,firstnamex ()" against the stated Nextcloud 27 setup, then trace the synchronization path that returns the "forbidden" error. Done means synchronization completes while the matching directory is ignored.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.