DO NOT REPLY [Bug 31101] New: - filenames that are url-encoded with some browsers are not correctly decoded

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31101>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=31101

filenames that are url-encoded with some browsers are not correctly decoded

           Summary: filenames that are url-encoded with some browsers are
                    not correctly decoded
           Product: Slide
           Version: Nightly
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Minor
          Priority: Other
         Component: WebDAV Server
        AssignedTo: slide-dev@jakarta.apache.org
        ReportedBy: thomas.draier@codeva.net


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.

---------------------------------------------------------------------
To unsubscribe, e-mail: slide-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-dev-help@jakarta.apache.org