Scott Mitchell c4a8f95c3e HttpObjectAggregator doesn't check content-length header ... Motivation: The HttpObjectAggregator always responds with a 100-continue response. It should check the Content-Length header to see if the content length is OK, and if not responds with a 417. Modifications: - HttpObjectAggregator checks the Content-Length header in the case of a 100-continue. Result: HttpObjectAggregator responds with 417 if content is known to be too big.		2015-08-17 09:29:39 -07:00
..
src	HttpObjectAggregator doesn't check content-length header	2015-08-17 09:29:39 -07:00
pom.xml	Refactor tests for compression codecs	2015-04-10 15:50:20 +02:00