Skip to content

Allow for Non-Standard Charset Name #20

@s25g5d4

Description

@s25g5d4

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

throw new TypeError('unsupported charset in extended field')
. It is not my server and I have no way to ask them to change, so if you can fix this (either by accept utf8 or fallback to filename) that would be appreciated.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions