How to disable base64-encoded filenames in HttpClient/MultipartFormDataContent

Question

I'm using HttpClient to POST MultipartFormDataContent to a Java web application. I'm uploading several StringContents and one file which I add as a StreamContent using MultipartFormDataContent.Add(HttpContent content, String name, String fileName) using the method HttpClient.PostAsync(String, HttpContent).

This works fine, except when I provide a fileName that contains german umlauts (I haven't tested other non-ASCII characters yet). In this case, fileName is being base64-encoded. The result for a file named 99 2 LD 353 Temp Äüöß-1.txt

looks like this:

 __utf-8_B_VGVtcCDvv73vv73vv73vv71cOTkgMiBMRCAzNTMgVGVtcCDvv73vv73vv73vv70tMS50eHQ___

The Java server shows this encoded file name in its UI, which confuses the users. I cannot make any server-side changes.

How do I disable this behavior? Any help would be highly appreciated.

Thanks in advance!

score 11 · Answer 1 · answered Mar 10 '15 at 03:42

I just found the same limitation as StrezzOr, as the server that I was consuming didn't respect the filename* standard.

I converted the filename to a byte array of the UTF-8 representation, and the re-armed the bytes as chars of "simple" string (non UTF-8).

This code creates a content stream and add it to a multipart content:

        FileStream fs = File.OpenRead(_fullPath);
        StreamContent streamContent = new StreamContent(fs);
        streamContent.Headers.Add("Content-Type", "application/octet-stream");
        String headerValue = "form-data; name=\"Filedata\"; filename=\"" + _Filename + "\"";
        byte[] bytes = Encoding.UTF8.GetBytes(headerValue);
        headerValue="";
        foreach (byte b in bytes)
        {
            headerValue += (Char)b;
        }
        streamContent.Headers.Add("Content-Disposition", headerValue);
        multipart.Add(streamContent, "Filedata", _Filename);

This is working with spanish accents.

Hope this helps.

Note that multipart.Add(streamContent, "Filedata", _Filename) is not needed, multipart.Add(streamContent) is sufficient. Currently multipart.Add(streamContent, "Filedata", _Filename) will just skip the 2 last arguments since the header already exist, but it could change in the future (that it will overwrite\replace instead if skipping). — osexpert, Jul 17 '19 at 11:56

score 2 · Answer 2 · answered Dec 23 '16 at 07:21

I recently found this issue and I use a workaround here:

At server side:

private static readonly Regex _regexEncodedFileName = new Regex(@"^=\?utf-8\?B\?([a-zA-Z0-9/+]+={0,2})\?=$");

private static string TryToGetOriginalFileName(string fileNameInput) {
    Match match = _regexEncodedFileName.Match(fileNameInput);
    if (match.Success && match.Groups.Count > 1) {
        string base64 = match.Groups[1].Value;
        try {
            byte[] data = Convert.FromBase64String(base64);
            return Encoding.UTF8.GetString(data);
        }
        catch (Exception) {
            //ignored
            return fileNameInput;
        }
    }
    return fileNameInput;
}

And then use this function like this:

string correctedFileName = TryToGetOriginalFileName(fileRequest.FileName);

It works.

score 1 · Answer 3 · edited Oct 07 '21 at 13:31

1

In order to pass non-ascii characters in the Content-Disposition header filename attribute it is necessary to use the filename* attribute instead of the regular filename. See spec here.

To do this with HttpClient you can do the following,

   var streamcontent = new StreamContent(stream);
   streamcontent.Headers.ContentDisposition = new ContentDispositionHeaderValue("attachment") {
      FileNameStar = "99 2 LD 353 Temp Äüöß-1.txt" 
   };
   multipartContent.Add(streamcontent);

The header will then end up looking like this,

  Content-Disposition: attachment; filename*=utf-8''99%202%20LD%20353%20Temp%20%C3%84%C3%BC%C3%B6%C3%9F-1.txt

edited Oct 07 '21 at 13:31

Community

1
1

answered Feb 21 '14 at 14:38

Darrel Miller

139,164
32
194
243

Sadly the server doesn't seem to respect filename* or it's being base64-encoded as well, as the file still shows up with an encoded name in the UI of the application. As your example header looks URL-encoded I've also tried to URL-encode the filename, but the web application will show it as-is then, without decoding it. – Strezz0r Mar 04 '14 at 09:09

score 1 · Accepted Answer · answered Mar 07 '14 at 15:54

I finally gave up and solved the task using HttpWebRequest instead of HttpClient. I had to build headers and content manually, but this allowed me to ignore the standards for sending non-ASCII filenames. I ended up cramming unencoded UTF-8 filenames into the filename header, which was the only way the server would accept my request.

How to disable base64-encoded filenames in HttpClient/MultipartFormDataContent

4 Answers4

Linked