{"push_id":2101046747,"size":1,"distinct_size":1,"ref":"refs/heads/deprecation-header-encoding","head":"603ec491b1e78029dac4e4649ad7eba26551b6f6","before":"2172f06e96fd0a974f748cff8d3f106e4a1e5873","commits":[{"sha":"603ec491b1e78029dac4e4649ad7eba26551b6f6","author":{"name":"Jason Tedor","email":"158e602a35675d2a0b685478824aa5995557a235@tedor.me"},"message":"Correctly encode warning headers\n\nThe warnings headers have a fairly limited set of valid characters\n(cf. quoted-text in RFC 7230). While we have assertions that we adhere\nto this set of valid characters ensuring that our warning messages do\nnot violate the specificaion, we were neglecting the possibility that\narbitrary user input would trickle into these warning headers. Thus,\nmissing here was tests for these situations and encoding of characters\nthat appear outside the set of valid characters. This commit addresses\nthis by encoding any characters in a deprecation message that are not\nfrom the set of valid characters.","distinct":true,"url":"https://api.github.com/repos/jasontedor/elasticsearch/commits/603ec491b1e78029dac4e4649ad7eba26551b6f6"}]}
{"actor":{"display_login":"jasontedor"}}