[artifact:deploy] Uploading: org/scala-lang/scala-library/2.12.0-362aa5c-SNAPSHOT/scala-library-2.12.0-362aa5c-20141110.055550-1.jar to repository pr-scala at http://private-repo.typesafe.com/typesafe/scala-pr-validation-snapshots/ [artifact:deploy] Transferring 5437K from pr-scala [artifact:deploy] Unexpected end of file from server [artifact:deploy] An error has occurred while processing the Maven artifact tasks. [artifact:deploy] Diagnosis: [artifact:deploy] [artifact:deploy] Error deploying artifact 'org.scala-lang:scala-library:jar': Error deploying artifact: Error transferring file [artifact:deploy] Unexpected end of file from server
I lodged a support ticket about 12 hours ago. It is the hands of an engineer at JFrog, but we are still awaiting a diagnosis / fix.
Thanks for you patience,
Following our investigation and after analyzing logs of the relevant components and testing the issue in our end, here is what we found:This issue appeared after we have upgraded the Artifactory online Tomcat to a newer version that includes a few important security bug fixes.It seems that the Maven Ant Task is not using preemptive authentication so it sends an unauthenticated PUT request and start streaming the content of the resource. Artifactory respond to the PUT request with 401 challenge that requires the client to provide credentials, however, the newer version of Tomcat has a feature that cut the connection of the upload when responding with 401 challenge to the client. It seems that the client intercept the response incorrectly and don't know how do deal with it, therefore due to the connection that been closed, the client report on 'Error deploying artifact: Error transferring file, Unexpected end of file from server' and not answer the challenge with a new request that includes the authentication.From our tests, it seems that other clients other clients such as Maven and Ivy knows how to deal with it and have no similar issues.If it is possible, we suggest to check the option of upgrade the Maven Ant Task to a newer version and see if it knows how to deal with this situation.Another important direction is check if preemptive authentication can be enabled in Maven Ant Task can support so the client will send the authentication with the first request instead sending unauthenticated request and waiting to a 401 challenge. If this is possible, it will probably be the best solution.
You received this message because you are subscribed to the Google Groups "scala-internals" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scala-interna...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.