-
_From @Petermarcu on November 27, 2017 5:1_
@StefanoD opened this here: https://github.com/dotnet/core/issues/1106
According to https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Di…
-
attachment name can't support Chinese
all contain Chinese word attachment filename , return "filename":""
-
Required to be supported by a parser but not necessary by us for now
-
Let’s use the Pull Request model so that we can ensure the gem is always functioning in the master branch.
Currently, the latest master fails to build this document but it worked a few commits ago…
-
hi ,
i am using android-upload-service to upload a file with filename written in hebrew (utf-8 encoding),
on the other end i'm getting ????????? instead of the filename,
is there any way to set the ch…
-
RFC 2231 is now widely implemented. JavaMail should support it by default.
mail.mime.decodeparameters and mail.mime.encodeparameters should default
to true.
#### Affected Versions
1.4.5
#### Environm…
-
When RFC 2231 encoding was enabled by default (mail.mime.encodeparameters=true),
the mail.mime.encodefilename property that requests filenames be encoded using
the older (non-standard) MIME encoded wo…
-
When a long parameter value (e.g., a long file name) is set on a header in
a message, the long parameter value can result in a very long line in the
message. If the value contains whitespace (as file…
-
The [TODO](https://github.com/neomutt/neomutt/blob/b7c0d9abd67f23fb16f36834eb66ff25d06a2560/TODO) file says:
> When displaying MIME headers, rfc 2047 decoding is applied (which
> should not happe…
ghost updated
7 years ago
-
JavaMail 1.5 was supposed to encode parameter list values using RFC 2231
when necessary. The Content-Disposition "filename" parameter wasn't being
encoded because it was calling the ParameterList set…