Hi, My patch doesn't seem to come completely without troubles, though. I still find this a potentially valuable scenario; e.g. for a public repo with push access only over HTTP, but using secure digest authentication instead of sending the credentials in plaintext. One downside is that it causes a lot more HTTP requests, since libcurl initially tries without any authentication for (almost?) every request, doubling the number of requests made. Fetching works just fine, but pushing may fail on auth problems in some cases where it wouldn't fail otherwise, if only basic authentication was used and libcurl automatically used that without probing what authentication scheme the server uses. Things generally seem to work fine with Apache, but with Lighttpd, retrying with proper credentials may fail due to CURLE_SEND_FAIL_REWIND /* 65 - Sending the data requires a rewind that failed */. This issue can be fixed by another patch (that I'll send soon). Even after fixing that, there still seems to be some issues on some older curl versions; in particular, 7.16.3, shipped in OS X Leopard, returns error code CURLE_HTTP_RETURNED_ERROR instead of retrying properly with authentication. // Martin -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
