2017-09-05 6:26 GMT+09:00 Daniel Stenberg <[email protected]>: > Can you reproduce this problem with the curl command line tool over the > same proxy? (I want to find a way for me to hunt for this problem without > involving git) > > The curl command works well via the same proxy, this problem only occurs with git.
Can you run wireshark or otherwise get a trace to see exactly what the > proxy responds that curl seems to have a problem with? I will be able to do it, but it is difficult to send the detailed information, I'm sorry. Below is a part of the output of git by GIT_CURL_VERBOSE option witch sets CURLOPT_VERBOSE to curl_easy_setopt(). * Establish HTTP proxy tunnel to github.com:443 > CONNECT github.com:443 HTTP/1.1 Host: github.com:443 User-Agent: git/2.14.1 Proxy-Connection: Keep-Alive < HTTP/1.1 407 Proxy Authentication Required < Proxy-Authenticate: BASIC realm="****" < Cache-Control: no-cache < Pragma: no-cache < Content-Type: text/html; charset=utf-8 < Proxy-Connection: close < Connection: close < Content-Length: 4650 < * Ignore 4650 bytes of response-body * Establish HTTP proxy tunnel to github.com:443 * Proxy auth using Basic with user '****' > CONNECT github.com:443 HTTP/1.1 Host: github.com:443 Proxy-Authorization: Basic ******************************** User-Agent: git/2.14.1 Proxy-Connection: Keep-Alive * Proxy CONNECT aborted * CONNECT phase completed!
------------------------------------------------------------------- Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library Etiquette: https://curl.haxx.se/mail/etiquette.html
