Scott Mitchell a7135e8677 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:26:50 -07:00
..
binary	fix typo	2015-03-19 20:41:11 +01:00
AbstractMemcacheObject.java	Adhere to our getter/setter naming rules	2014-06-24 16:10:32 +09:00
AbstractMemcacheObjectAggregator.java	HttpObjectAggregator doesn't check content-length header	2015-08-17 09:26:50 -07:00
AbstractMemcacheObjectDecoder.java	codec-memcache: prefix abstract classes with Abstract.	2014-02-13 17:09:21 -08:00
AbstractMemcacheObjectEncoder.java	Returns after encoding each message not do check following instance types	2015-03-19 20:43:59 +01:00
DefaultLastMemcacheContent.java	Enable a user specify an arbitrary information with ReferenceCounted.touch()	2014-02-13 18:16:25 -08:00
DefaultMemcacheContent.java	Adhere to our getter/setter naming rules	2014-06-24 16:10:32 +09:00
FullMemcacheMessage.java	Enable a user specify an arbitrary information with ReferenceCounted.touch()	2014-02-13 18:16:25 -08:00
LastMemcacheContent.java	Adhere to our getter/setter naming rules	2014-06-24 16:10:32 +09:00
MemcacheContent.java	Enable a user specify an arbitrary information with ReferenceCounted.touch()	2014-02-13 18:16:25 -08:00
MemcacheMessage.java	Enable a user specify an arbitrary information with ReferenceCounted.touch()	2014-02-13 18:16:25 -08:00
MemcacheObject.java	Adhere to our getter/setter naming rules	2014-06-24 16:10:32 +09:00
package-info.java	Implementing the Binary Memcache protocol	2014-02-13 15:29:38 -08:00