`
the filename 1 and filename2 was recoginzed as the url code.
is it a bug?
I think it would be better if decode the filename in the function of the mime::merge_attributes?
cause I founded that the filename0 part was the nomal text decoded ,and the filename1 part was the text encoded.
the string_t mime::parse_header_value_attribute(const string& attr_value) const only parsed the first line of the Content-Disposition
the mime data example: ` Content-Type: application/pdf;
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
` the filename 1 and filename2 was recoginzed as the url code. is it a bug?
I think it would be better if decode the filename in the function of the mime::merge_attributes? cause I founded that the filename0 part was the nomal text decoded ,and the filename1 part was the text encoded.