On Tue, 1 Dec 2009, Shawn O. Pearce wrote: > Martin Storsj? <martin@xxxxxxxxx> wrote: > > When using multi-pass authentication methods, the curl library may need > > to rewind the read buffers used for providing data to HTTP POST, if data > > has been output before a 401 error is received. > > In theory, since the cURL session stays active, we would have > received the 401 authentication error during the initial > "GET $GIT_DIR/info/refs?service=git-$service" request, and the subsequent > "POST $GIT_DIR/git-$service" requests would automatically include the > authentication data. > > That's theory. Reality doesn't always agree with my theories. :-) As Tay said - his "maintain curl sessions" patch should make this redundant in most cases. But in case request pattern gets changed or if the curl session for some other reason isn't able to authenticate on the first try, this is a quite non-intrusive way of ensuring that these requests can be restarted. // 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