Various multipart fixes, close #296, #297, #298
[maven-release-plugin] prepare release async-http-client-1.7.16
[maven-release-plugin] prepare for next development iteration
Fix Netty privider's ReaperFuture messages, close #281
Make idleConnectionTimeout effective when less than requestTimeout, backport #120
Fixes #302
Fix timeout tests, close #304
Use StringBuilders instead of StringBuffers, close #305
Upgrade Netty 3.6.6.Final, close #306
Upgrade Slf4j 1.7.5, close #307
Backport 13b9bd45e44b8dfd9e257add65eb40374622970c
Remove additional CRLF when there's no Content-Disposition, close #309
Make sure onClose is called once
[maven-release-plugin] prepare release async-http-client-1.7.17
[maven-release-plugin] prepare for next development iteration
Added an option for netty connection pool to limit the time when connection can be put back to pool.
In case of Amazon Cloud DNS records can change in seconds, and taking into account that AHC caches already resolved connection and never re-resolve DNS records if response if ok, introducing option to limit life for cached connection, to be able to gracefully route traffic to new host in case dns records changed.

Conflicts:

	src/main/java/com/ning/http/client/AsyncHttpClientConfig.java
	src/main/java/com/ning/http/client/providers/netty/NettyConnectionsPool.java
SSL connection pooling doesn't work with grizzly provider
Merge pull request #311 from kumai/fix/grizzly-ssl-connection-cache

SSL connection pooling doesn't work with grizzly provider
Uses DateUtil.millisTime() instead of System.currentTimeMillis()
Merge pull request #310 from kumai/feature/connection-ttl

Added an option for netty connection pool to limit the time when connect...