On 23/01/2013, at 4:47 PM, Daz DeBoer <[email protected]> wrote:
> G'day > > Another issue has been discovered with 1.4-rc-2: > http://issues.gradle.org/browse/GRADLE-2650. Is this a new issue in this release? What change sparked it? > > It's unfortunate that the symptoms of this issue are very similar to > http://issues.gradle.org/browse/GRADLE-2641 which was fixed in 1.4-rc-2. This > similarity meant that we originally thought it was the same issue. > > It's possible that the fix is as simple as setting http.keepAlive = "true" > explicitly in our code, to workaround the bug in HttpClient 4.2.2. I'm > waiting to hear back on this front. > > If that doesn't fix the issue, we might want to consider introducing a system > property that would permit a user to specify which authentication scheme > should be used. That would also allow users to avoid the needless attempts at > NTLM authentication with every request, as well as removing the warning that > is often emitted about NEGOTIATE credentials not being available. > There is actually a standard java system property for this, so we could > simply honour that preference: > (http://docs.oracle.com/javase/7/docs/technotes/guides/net/http-auth.html) > http.auth.preference="scheme" > Finally, we could consider upgrading to HttpClient 4.2.3, which may have > resolved this issue. I think we should do this for 1.5, as the new version > has vastly improved NTML authentication that might allow us to replace the > JCIFS implementation we currently use. We could use a custom value like > http.auth.preference="jcifs" to permit users to continue using the old > implementation (until we are confident the new implementation works). > > -- > Darrell (Daz) DeBoer > Principal Engineer, Gradleware > http://www.gradleware.com -- Luke Daley Principal Engineer, Gradleware http://gradleware.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
