Edited Issue: Content-type is parsed incorrectly for atom feeds [213]

According to http://www.ietf.org/rfc/rfc5023.txt Content-type of atom feeds can looks like this:

application/atom+xml; charset=UTF-8; type=entry or application/atom+xml; type=entry; charset=UTF-8

This is perfectly legal textual body, however web::http::details::parse_content_type_and_charset can't parse such a string and http_msg_base::_extract_string() throws http_exception(textual_content_type_missing)