http: fix charset detection of extract_content_type()
authorYi EungJun <eungjun.yi@navercorp.com>
Tue, 17 Jun 2014 22:11:53 +0000 (07:11 +0900)
committerJunio C Hamano <gitster@pobox.com>
Tue, 17 Jun 2014 22:25:00 +0000 (15:25 -0700)
extract_content_type() could not extract a charset parameter if the
parameter is not the first one and there is a whitespace and a following
semicolon just before the parameter. For example:

text/plain; format=fixed ;charset=utf-8

And it also could not handle correctly some other cases, such as:

text/plain; charset=utf-8; format=fixed
text/plain; some-param="a long value with ;semicolons;"; charset=utf-8

Thanks-to: Jeff King <peff@peff.net>
Signed-off-by: Yi EungJun <eungjun.yi@navercorp.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
No differences found