Final changes for AsyncHttpClient#258.

When dealing with http expectations, check to see if we're writing a file and if so, set the content-length then as the FileBodyHandler invocation is delayed in this scenario.

Author: rlubke

providers/grizzly/src/main/java/com/ning/http/client/providers/grizzly/GrizzlyAsyncHttpProvider.java

@@ -543,6 +543,14 @@ boolean sendRequest(final FilterChainContext ctx,
             BodyHandler handler = bodyHandlerFactory.getBodyHandler(request);
             if (requestPacket.getHeaders().contains(Header.Expect)
                     && requestPacket.getHeaders().getValue(1).equalsIgnoreCase("100-Continue")) {
+                // We have to set the content-length now as the headers will be flushed
+                // before the FileBodyHandler is invoked.  If we don't do it here, and
+                // the user didn't explicitly set the length, then the transfer-encoding
+                // will be chunked and zero-copy file transfer will not occur.
+                final File f = request.getFile();
+                if (f != null) {
+                    requestPacket.setContentLengthLong(f.length());
+                }
                 handler = new ExpectHandler(handler);
             }
             context.bodyHandler = handler;
@@ -2219,9 +2227,7 @@ public boolean doHandle(final FilterChainContext ctx,
             final File f = request.getFile();
             requestPacket.setContentLengthLong(f.length());
             final HttpTransactionContext context = getHttpTransactionContext(ctx.getConnection());
-            if (!SEND_FILE_SUPPORT
-                    || requestPacket.isSecure()
-                    || requestPacket.getHeaders().contains(Header.TransferEncoding)) {
+            if (!SEND_FILE_SUPPORT || requestPacket.isSecure()) {
                 final FileInputStream fis = new FileInputStream(request.getFile());
                 final MemoryManager mm = ctx.getMemoryManager();
                 AtomicInteger written = new AtomicInteger();