Closed carsonip closed 6 years ago
Can one of the admins verify this patch?
Please make sure that all tests pass.
The test is fixed but it isn't neat. In parse_header_value
, non-ascii value will actually be handled and it will raise DecodeError.
I do not quite get what the bug is. Are you saying that a unicode attachment name is not properly encoded by the library?
Sometimes email providers don't handle unicode attachment names properly and send them out directly as unicode characters in 'name' or 'filename' parameters. Flanker should be able to handle these cases and decode them properly.
Hey @carsonip sorry for letting this slip. Can you rebase it so I can merge?
Rebased. Did a force push. Please check.
@mailgun-ci test this please
@mailgun-ci retest this please
The default tests are running and passing when we trigger a job manually but the same jobs aren't being triggered by the PR webhooks. Might have something to do with the PR being older.
Non-ascii param will no longer raise DecodingError, as shown in the old broken_ctype_test. This bug can be reproduced by sending an attachment in gmail with non-ascii name. The bug is fixed by tuning regex. Non-ascii params still have to be double quoted.