On 30/03/2012, at 1:19 PM, Daz DeBoer wrote: > On 29 March 2012 17:31, Adam Murdoch <[email protected]> wrote: > * We need to deal with the case where a server does not handle the HEAD > request (e.g. stuff hosted at googlecode). > > Good point. That's something we don't currently handle. Although > googlecode.com is broken, and it would be nice to trust the HEAD request on > other servers. That would mean coding an exception algorithm for googlecode, > I guess. Not fundamentally different from knowing etag==sha1 for Nexus, or > using the special Artifactory SHA1 header, I guess. > Daz
There are some other cases where the HEAD request fails but the GET request would succeed, that we should think about. One example is where you get a 403 'forbidden' or a 405 'method not supported' response to the HEAD request, regardless of whether the resource exists or not (can't recall exactly where this was happening; it's in jira somewhere). I think for these response codes, we should continue on to the GET SHA1 request. -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
