Bug 105139

Summary: Garbaged Japanese file name via downloading from iFolder3 web.
Product: [iFolder] iFolder Denali Reporter: Katsuya Takahashi <katakahashi>
Component: Web AccessAssignee: Rob Lyon <rlyon>
Status: VERIFIED FIXED QA Contact: Jared Allen <jpallen>
Severity: Critical    
Priority: P5 - None    
Version: iFolder Denali   
Target Milestone: 3.2   
Hardware: All   
OS: All   
Whiteboard:
Found By: Localization Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Destroy Japanese file names
Destroy Japanese file names

Description Katsuya Takahashi 2005-08-17 10:55:11 UTC 
OES 812, client XP + Firefox 1.04 and IE6.0.2900.2180, NLDSP2RC6+FF104

iFolder3 Web can upload and display Japanese file name with IE and FF 
correctly. But they destroy the Japanese file name at the downloading.
FF destroys only the file name. IE destroys the file name. And he also lost the 
mime type(extensions).
Comment 1 Katsuya Takahashi 2005-08-17 10:56:04 UTC 
Created attachment 46270 [details]
Destroy Japanese file names
Comment 2 Katsuya Takahashi 2005-08-17 10:57:26 UTC 
Created attachment 46271 [details]
Destroy Japanese file names
Comment 3 Rob Lyon 2005-08-17 14:56:28 UTC 
Is the file okay?  Is it only the filename that gets mangled?
Comment 4 Rob Lyon 2005-08-17 23:38:57 UTC 
This appears to just be a filename issue.  Downgrading to Normal and moving to 
future.  It is too late to fix this bug at this point.
Comment 5 Rob Lyon 2005-08-18 17:42:16 UTC 
I discovered that this is a known ASP.NET issue and that Microsoft is working 
on a solution.  I can do a work-around with URL encoding, but it does not help 
Firefox, only IE.
Comment 6 Katsuya Takahashi 2005-08-19 01:35:38 UTC 
Almost users use IE on Windows for their client. So your work-around will be 
help for them. Please go ahead to implement it.
Comment 7 Katsuya Takahashi 2005-08-19 01:36:53 UTC 
I made mistake to set status. I re-open this.
Comment 8 Rob Lyon 2005-08-19 04:11:50 UTC 
I implemented the work-around for IE, but it didn't make SP1.
Comment 9 Rob Lyon 2005-08-19 04:12:19 UTC 
fixed in CVS
Comment 10 Katsuya Takahashi 2005-10-25 08:17:11 UTC 
Does the fix include OES SP2 (current development build of SP2)?
Comment 11 Rob Lyon 2005-10-25 13:30:26 UTC 
Yes