A customer (see the Comments section for details) indicates that if the new plug-in makes an HTTP GET request for a jar file, and the server provides a chunked response, the plug-in will fail to download the jar file. Apparently, the old plug-in works fine in this scenario.

Unfortunately a test case was not provided.

We should investigate how the HTTP stack in the core JDK handles chunked responses and see, for example, if there is any system property setting or similar which we have missed porting over from the old plug-in to the new plug-in.

A few members of the networking team are on the CC: list; suggestions of what might be going wrong would be appreciated. Any difference here is very low-level, underneath both the new plug-in as well as the deployment workspace's common DownloadEngine class which handles the fetching of content from the server.