Bugfix: Handle Content-Type headers with charset
authorFelix Geisendörfer <felix@debuggable.com>
Thu, 28 Jan 2010 16:16:18 +0000 (17:16 +0100)
committerRyan Dahl <ry@tinyclouds.org>
Sat, 30 Jan 2010 02:04:48 +0000 (18:04 -0800)
commitac2abe5b1e5e872a587da3593e8d764512f05438
tree5d503055973c0e623226aebd06c5a43412ec6bb8
parentb06dda1f5e6d89fc8412a7b14bb23a6582a40850
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.
lib/multipart.js
test/mjsunit/test-multipart.js