UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.62 Safari/537.36

Steps to reproduce the problem:
1. Create a file with a special character in it's name, ie. "Stecker fÅr MWM Modul"
2. Upload file to API endpoint (I'm using WebApi2 .NET 4.6)
3. In the API, notice that the 'content-disposition' header has a filename that contains an 'A' and the ASCII hex code for the degree symbol (0xb0), ie. "Stecker fA(0xb0)r MWM Modul" (see attached image)

What is the expected behavior?
The Å in the filename should be maintained as a single character instead of it's component ASCII characters (I guess?).

What went wrong?
It would seem that these special characters are being broken into their component ASCII characters.

Did this work before? N/A 

Chrome version: 62.0.3202.62  Channel: stable
OS Version: 10.12.6 (Sierra)
Flash Version: 

This seems to be isolated to my colleagues that use Chrome 62 on their Macbooks. I'm 99.5% confident this is a new issue brought on by the v62 release. I'm using the same release on Windows and do not have this issue.

I've attached a screenshot from my log file that shows the 'content-disposition' header as it was provided to the API. Hopefully that helps serve as evidence.
 

Deleted: mac-chrome issue.png 1.6 KB

	mac-chrome issue.png 1.6 KB View Download