Enrique Tobis <enrique.to...@twosigma.com> writes: > Hey! > > I'm really sorry to hear that. > > That change should enable more forms of authentication with your > proxy, but it does cause libcurl to choose the one it finds most > secure, according to the docs > (http://curl.haxx.se/libcurl/c/CURLOPT_HTTPAUTH.html) What kinds of > authentication does your proxy use?
Good line of thought. The answer would reveal what non-working authentication form the proxy claims to support is chosen because libcurl considers more secure than the one the user wants to use. I'd imagine that the next step after that would be to make the list of authentication forms configurable so that the user can say "hey my proxy claims to support this one but it does not work" to skip it? That sounds like a similar approach as what we did for SSL ciphers in f6f2a9e4 (http: add support for specifying an SSL cipher list, 2015-05-08) where some people had problems with certain cipher the server/client claimed to support when it was in fact broken. Thanks. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
