Bugfix: Handle Content-Type headers with charset
Some HTTP clients include a charset parameter in the Content-Type, e.g: multipart/form-data; charset=utf-8; boundary=0xKhTmLbOuNdArY This patch makes the multipart parser more forgiving towards unexpected information included in the Content-Type header.
parent
b06dda1f
Please register or sign in to comment