I am using HttpClient 4.2.2 to upload a file with non ascii characters in the name using a multipart request. The issue I'm running into is the character encoding used for the filename in the header is always US-ASCII instead of using the charset on the HttpMultipart MIME entity. When constructing a new MultipartEntity I pass in a mode of STRICT which, after looking at the source, I found will always use MIME.DEFAULT_CHARSET (US-ASCII). If I use the BROWSER_COMPATIBLE mode then the specified charset is used, but this mode will only write Content-Disposition and Content-Type headers. Is there a reason that a multipart request with a mode of STRICT will always use US-ASCII for header values?
Thanks, Brad
