OpenSearch/core
Jason Tedor 766d29e7cf
Correctly encode warning headers
The warnings headers have a fairly limited set of valid characters
(cf. quoted-text in RFC 7230). While we have assertions that we adhere
to this set of valid characters ensuring that our warning messages do
not violate the specificaion, we were neglecting the possibility that
arbitrary user input would trickle into these warning headers. Thus,
missing here was tests for these situations and encoding of characters
that appear outside the set of valid characters. This commit addresses
this by encoding any characters in a deprecation message that are not
from the set of valid characters.

Relates #27269
2017-11-06 13:20:30 -05:00
..
licenses Upgrade to Jackson 2.8.10 (#27230) 2017-11-06 10:20:05 +01:00
src Correctly encode warning headers 2017-11-06 13:20:30 -05:00
build.gradle Upgrade to Log4j 2.9.0 2017-08-31 09:54:35 -04:00