Renaming a file with a slash in the filename makes the file inaccessible (dataloss)

[tbsbdr]

Initial Checklist

• I understand this is a bug report and questions should be posted in the Community Discussions
• I searched issues and couldn’t find anything (or linked relevant results below)

Bug Description

• Renaming a file with a slash in the filename makes the file inaccessible
• Cant' create or upload files with "" in filename
• Downloading a file with a slash in the filename fails

Reproduction Steps

rename file and make it inaccessible

1. there is an existing file vacation.jpg
2. rename the file to vaca\tion.jpg
3. click on vaca\tion.jpg to open it
4. cant open or download file

other issues you can create with a backslash:

Cant create file:
2. New -> Create Markdown1. Filename bla\bla.txt

1. Error: "failed to create file"

cant download file

1. select existing resource
2. rename it to bla\bla
3. download bla\bla
4. Error: download failed
5. renaming it back to a name without a slash does not work, error "failed to rename bla\bla" --> file can not

cant upload file

1. create lcoal file bla\bla
2. upload bla\bla (drag and drop or via "upload"
3. error: "Parent folder does not exist"

Expected Outcome

• create / upload / download of files with backslash is possible or
• tell the user, that the filename must not contain a backslash and have no files with backslashes in the cloud

Actual Outcome

• can not upload/download/create files with backslash in filename

[tbsbdr]

@kulmann Asessing as P2, because if I rename the file, I can not download it any more and renaming it back to a proper name is also not possible -> dataloss.

[JammingBen]

I tried with my local dev setup and couldn't reproduce the issue. File names with any special chars (except forward-slashes, those are forbidden) can be opened/edited/deleted without a problem.

However, on the demo instance as well as locally with our compose project I can reproduce this error, not only with a backslash \, but also with a hash # in the filename. I think this should work though? @micbar @rhafer do you have any insight, maybe somehow related to the storage?

create lcoal file bla\bla
upload bla\bla (drag and drop or via "upload"
error: "Parent folder does not exist"

The error message is very misleading indeed, the web client shows it on every 412 error. We should adjust that.