error parse when have semicolon at last about content-disposition

[dougwilson]

Correct, because that is not a valid header string, as specified by RFC 6266: https://tools.ietf.org/html/rfc6266

[magicode]

But not all websites conform to RFC 6266, such as https://www.fotolia.com
It is possible they do this purposely in order to disable scripts.
Perhaps it makes sense to add an option of "loose" parsing, for websites that don't follow the standards.‏

[dougwilson]

Hi @magicode, you're certainly welcome to make a pull request to implement a "lax" mode of parsing! If we are not parsing according to the standard, we may want to lay out exactly what the parsing algorithm would be. Can you do that as well? Perhaps it can build off of pre-existing algorithms, like some web browsers (assuming they are not crazy buggy!).

Otherwise, I suggest you run your own header cleanser before trying to parse invalid headers if you don't want the parser to tell you it's invalid.