)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":9107,"name":"Victor Stinner","email":"vstinner@redhat.com","username":"haypo"},"change_message_id":"751a238ce3eef6dcbf995ebdfa27aad3c0863dbb","unresolved":false,"context_lines":[{"line_number":12,"context_line":"time, we now adhere to RFC 7230\u0027s requirement that header field-content"},{"line_number":13,"context_line":"consist of printable USASCII characters (at least, for X-Storage-Policy)"},{"line_number":14,"context_line":"by URL-encoding the policy name. As a result, most existing policies"},{"line_number":15,"context_line":"will not notice any change."},{"line_number":16,"context_line":""},{"line_number":17,"context_line":"Change-Id: Ia59aa02e51610b8b2470a7602f2624ab45ad4b0e"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":3,"id":"9a41bdd9_c90b00d5","line":15,"updated":"2015-07-15 16:33:22.000000000","message":"It is possible to send non-ASCII data in header values using a MIME encoding like \u003d?UTF-8?Q?...?\u003d. I don\u0027t know at which level this encoding should be handled.\n\nThe Python 3 HTTP client encodes Unicode to ISO-8859-1 (aka \"latin1\") for HTTP header values. It uses the following code to parse HTTP header values:\n\n    hstring \u003d b\u0027\u0027.join(headers).decode(\u0027iso-8859-1\u0027)\n    return email.parser.Parser(_class\u003d_class).parsestr(hstring)\n\nThe email module is probably used to handle MIME encodings.\n\nI guess that in practice, some clients and servers don\u0027t care of the standards and use directly UTF-8 in header values.","commit_id":"d593e201820e3af7b6f40436897aea7dc7ce6fe6"}]}
