Hi Fred, The problem won't be due to the virus checking as I am fairly sure we don't run that on the company unix servers. I tried another repository product and that failed in the same way. I have used tcpmon to look at the HTTP protocol between the artifactory and the remote repository and I notice that the transfer-encoding header on the GET is set to chunked and I'm wondering if this might have something to do with it. The xerces jar appears to download correctly but this error then appears as it is written out locally. I wonder whether it is possible to enable some log4j type trace so that I can get a stack trace at the point of failure in artifactory ?
-- View this message in context: http://forums.jfrog.org/Bad-chunk-size-downloading-xerces-xercesImpl-2-9-1-tp6607551p6609946.html Sent from the Artifactory - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ 10 Tips for Better Web Security Learn 10 ways to better secure your business today. Topics covered include: Web security, SSL, hacker attacks & Denial of Service (DoS), private keys, security Microsoft Exchange, secure Instant Messaging, and much more. http://www.accelacomm.com/jaw/sfnl/114/51426210/ _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
