i've got an issue with some navigators, when using non-ascii characters in filenames. the standards does not define if an url-encoded filename should be encoded using utf-8 or another encoding. i've written an alternative method of URLUtil.URLDecode() that first tries to determine if the string can be an utf-8 string, and then use this encoding instead of the default encoding . that does not work for 100% of all strings, since sometimes a string can look like an utf-8, but this is occurs extremely rarely, as you need to have a very specific sequence of special characters. the problem occurs especially with characters in unicode range 00A0 - 00FF, which are alternatively encoded in utf-8 or iso-8859-15.
Created attachment 12662 [details] patch for WebdavUtils with new URLDecode
Patch applied