nextcloud / nextcloud/server

[Bug]: consecutive and non breaking spaces in folder name breaks folder access with Q&D fix !

Open
#48,136 17 comments 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

0. Needs triage 28-feedback bug 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

I have a folder with a single quote in it ( ' ) and a plus sign in it ( + ) I expected that to be the problem, but when I created a test folder named te+s't there was not any problem in accessing that folder including its test files.

Then I noticed that the problem folder also contained two spaces. I first tested with one space "t e+s't". That also did not result in any problems. But adding a second space after the first one all access to that folder was lost via the web interface and also the desktop client gave errors (I run windows 10 desktop client version 3.14.0)

Steps to reproduce
  1. create a folder with name "t e+s't" (TWO spces between the 't' and the 'e' !)
  2. sync via the desktop client
  3. see the errors mounting..
Expected behavior

I understand two spaces is a bit odd.. but it can happen.. and should work..

Nextcloud Server version

28

Operating system

RHEL/CentOS

PHP engine version

PHP 8.1

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

I am hesitant to do more testing since I am unable to correct the problem.

I use nextcloud with S3 for data storage. The file id's are there. I simply can't access them. A problem in the DAV connector ?

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.