Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Handle non-ascii characters in parameter values.
When embedding inline emoji, Outlook Web App generates headers that look like this: Content-Type: image/png; name='OutlookEmoji-π.png' It looks like handling parametrized headers containing non-ASCII characters was explicitly not supported previously. It's not clear to me why. The parameter-splitting code works just fine with values like these, though it would fail to correctly parse if e.g. the header name contained non-ascii characters.
- Loading branch information