Hey there! Thanks for such a great tool!

It seems that there is a problem with filename* decoding for multipart data. Having the content-disposition header like that for a part "form-data; name=fileName; filename*=utf-8''1_%D0%9B%D0%B8%D1%81%D1%821.html" file callback provides incorrect filename.

I've been digging into it recently and noticed something odd.

parseParams internally decodes filename into specified encoding, so parsed contains already decoded filename. On line 159 filename is decoded again having binary as current encoding and returns incorrect result.