Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

%20 and such URI codes are causing problems on a step called URIdecode in parsing the webdav result. #11646

Closed
MparkG opened this issue Oct 5, 2018 · 4 comments

Comments

@MparkG
Copy link

MparkG commented Oct 5, 2018

Steps to reproduce

  1. have files named with %20 or %28 in their name in a folder, e.g.
    %28ebook%20-%20german%29%20Gesetzestexte%20-%20Betriebsverfassungsgesetz%20%28.pdf
  2. Try to show that folder in nextcloud
  3. no profit.

Expected behaviour

The File List should be displayed.-

Actual behaviour

The Loading circle rotates endlessly, whilst in the console this error appears:
Uncaught (in promise) URIError: URI malformed
at decodeURIComponent ()
at Client.parseFileInfo (client.js:283)
at client.js:407
at Function.
.map._.collect (core.js:185)
at Client._parseResult (client.js:406)
at client.js:488

Server configuration

Nextcloud version: (see Nextcloud admin page)
14.something, bug appeared with update to 14.

@nextcloud-bot
Copy link
Member

GitMate.io thinks possibly related issues are #3738 (Webdav), #1502 (There were some problems with the code integrity check), #7365 (WebDAV PROPFIND results in 503 from browser), #5088 (Bearer auth backend causes problems with several dav clients), and #5947 (webDAV PROPFIND).

@kuhnline
Copy link

kuhnline commented Oct 6, 2018

I have user user with 2 folders in his root folder named
Job 90% CD
Job 100% CD

so his root folder would not load at all - just a spinning wheel, even if you let it run all day

I renamed the folders to
Job 90percent CD
Job 100percent CD

and the problem is solved.
But it wasted 2 hours of my time to figure this out.

These folders have existed since Version 12 so this error is new with Version 14.

@icewind1991
Copy link
Member

I can't reproduce this issue with either nc14.0.4 or 15.0.0, all combination of filenames with '%' in them work as expected

@juliusknorr
Copy link
Member

Yes, should be fixed in >=14.0.4 with #11744

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants