I don't have strong opinion. Just for the note. This make forcibly the filename encode
with rfc 6266. So older browser will not work after this change. Do we need to leave
a way to output raw-filenames?
This issue is to have a discussion, but I'll also loop in some security folks @mikesamuel@empijei, to help evaluate or just beware of the update.
The text was updated successfully, but these errors were encountered:
@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.)