Webdav don't support illegal characters like \/:*?<>| and leading and trailing whitespace.

[arkaroy14]

I have used mega-cmd in ubuntu 20.04 but when i webdav my folder i see some folders whose name having those illegal character /:*?<>| and leading and trailing whitespace can't open those.
But this type of error i only see in windows file system when i mounted.
Ubuntu should support those character.
Please help me so i can open those folder in webdav mode
Example folder name " Folder name : 1"
This i can't open in webdav mode as it is containing colon.
Thanks please suggest anything..

[polmr]

Hi @arkaroy14
You are right, MEGA supports those characters but MEGAcmd webdav proxy is failing to digest that.
For the moment, unfortunately you would need to refrain from using those problematic names via webdav.
Apologies for the inconvenience

[arkaroy14]

Hi @polmr
Is there any chance in future this problem will be solved?
It is very tough for me to change all names..
If there could be anything like auto rename to solve this problem.
Like for example google drive file stream app auto remove those illegal characters and whitespace which windows don't support when i mount my google drive.
So this type of feature would help.

[polmr]

We will eventually fix that, but I can't give an estimation date yet.
This could help you:

IFS=$'\n'; for i in $(mega-find / --pattern="*:*"); do mega-mv "$i" "${i/:/_}"; done

It will attempt to rename all files/folder in your MEGA account with : in the name by replacing : by _. But it will fail if there are 2 elements with : in the path though ;-).
If you want to be sure and review each of the movements, use:

IFS=$'\n'; for i in $(mega-find / --pattern="*:*" | grep :); do echo mega-mv '"'$i'"' '"'${i/:/_}'"'; done

And just copy-paste those you want

[dvukolov]

Is there anything we could do to help make MEGAcmd webdav proxy play nicely with all characters?

[sergiohs84]

Hi @arkaroy14 and @dvukolov, and thanks for reporting.

I've opened an internal ticket to look into the issue. If we decide to implement a workaround, you will eventually see the fix included in a future release. The reference ID is SDK-1500.

Thanks