We have an issue when users when users upload a UTF-8 encoded file names.  As
far as we can tell the brwoser encodes the file name correctly:

Hex dump of the filename encoded by IE7 recorded with Wireshark:
00000C4F 20 66 69 6c 65 6e 61 6d 65 3d 22 43 3a 5c 44 6f filenam e="C:\Do
00000C5F 63 75 6d 65 6e 74 73 20 61 6e 64 20 53 65 74 74 cuments and Sett
00000C6F 69 6e 67 73 5c 41 64 6d 69 6e 69 73 74 72 61 74 ings\Adm inistrat
00000C7F 6f 72 5c 4d 79 20 44 6f 63 75 6d 65 6e 74 73 5c or\My Do cuments\
00000C8F 44 6f 77 6e 6c 6f 61 64 73 5c d7 9e d7 99 d7 9b Download s\......
00000C9F d7 90 d7 9c 20 d7 a7 d7 95 d7 93 d7 95 d7 a8 d7 .... ... ........
00000CAF 95 d7 91 d7 a1 d7 a7 d7 99 2e 64 6f 63 78 2e 64 ........ ..docx.d
00000CBF 6f 63 78 22 0d 0a 43 6f 6e 74 65 6e 74 2d 54 79 ocx"..Co ntent-Ty

And with UFT-8 decoder is it displayed as the right file name, but when we
process that attachment:

        ContentDisposition disposition = attachment.getContentDisposition();
        String fileName = null;
        if (disposition != null) {
            fileName = disposition.getParameter("filename")

it comes back all garbled - the message encoding is set to UTF-8.  

Does CXF is not using the correct encoding when reading those file names?








--
View this message in context: 
http://cxf.547215.n5.nabble.com/Getting-UTF-8-encoded-filenames-from-Content-disposition-tp5713046.html
Sent from the cxf-user mailing list archive at Nabble.com.

Reply via email to