Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
mime/multipart: encode non-US-ASCII characters in Content-Disposition #33801
I am coming here from CL https://go-review.googlesource.com/c/go/+/190217 where @pascaldekloe has submitted a change that makes *mime/multipart.Writer generate a "Content-Disposition" value after invoking mime.FormatMediaType instead of using a quote escaper.
@pascaldekloe, what is the rationale for / impact of the proposed change?
Is this a feature request to support non-ASCII value for those names, or a bugfix for names that RFC requires the library is required to support?
Either way, why is there no corresponding documentation change in the CL? (Presumably the change widens the set of acceptable names, so the doc comment should probably mention which names are acceptable either way.)