Bug 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
Status: RESOLVED FIXED
Alias: None
Product: Slide
Classification: Unclassified
Component: WebDAV Server (show other bugs)
Version: Nightly
Hardware: All All
: P3 minor (vote)
Target Milestone: ---
Assignee: Slide Developer List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-07 17:43 UTC by Thomas Draier
Modified: 2004-11-16 19:05 UTC (History)
0 users



Attachments
patch for WebdavUtils with new URLDecode (3.46 KB, patch)
2004-09-07 17:50 UTC, Thomas Draier
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Draier 2004-09-07 17:43:49 UTC
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.
Comment 1 Thomas Draier 2004-09-07 17:50:01 UTC
Created attachment 12662 [details]
patch for WebdavUtils with new URLDecode
Comment 2 Oliver Zeigermann 2004-09-08 04:16:42 UTC
Patch applied