-
-
Notifications
You must be signed in to change notification settings - Fork 46
Closed
Description
Hello,
I encountered a server that returns content-disposition: attachment; filename="file.png"; filename*=utf8''file.png which is, according to RFC 5987, malformed because the charset should be utf-8, rather than utf8. When trying to decode content-disposition, it will fail at
Line 286 in 9908a22
| throw new TypeError('unsupported charset in extended field') |
utf8 or fallback to filename) that would be appreciated.Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels