连接后从代理收到 HTTP 代码 501
Received HTTP code 501 from proxy after CONNECT
每当我尝试从 bitbucket 克隆存储库时，都会出现以下错误：
fatal: unable to access 'https://user_name@bitbucket.org/user_name/repo_name.git/': Received HTTP code 501 from proxy after CONNECT
不明白是什么问题。我正在从 bitbucket 存储库 web 复制 git clone 命令。我也设置了 git http.proxy 但是没用。
如果需要更多信息，请告诉我。
谢谢
显然，您的代理不支持 HTTP CONNECT tunneling，这就是它以 HTTP 501 (Not implemented) 代码响应的原因：
HTTP CONNECT tunneling
A variation of HTTP tunneling when behind an HTTP Proxy Server is to
use the "CONNECT" HTTP method.
In this mechanism, the client asks an HTTP Proxy server to forward the
TCP connecting to the desired destination. The server then proceeds to
make the connection on behalf of the client. Once the connection has
been established by the server, the Proxy server continues to proxy
the TCP stream to and from the client. Note that only the initial
connection request is HTTP - after that, the server simply proxies the
established TCP connection.
This mechanism is how a client behind an HTTP proxy can access
websites using SSL (i.e. HTTPS).
Not all HTTP Proxy Servers support this feature, and even those that
do, may limit the behaviour (for example only allowing connections to
the default HTTPS port 443, or blocking traffic which doesn't appear
to be SSL).
每当我尝试从 bitbucket 克隆存储库时，都会出现以下错误：
fatal: unable to access 'https://user_name@bitbucket.org/user_name/repo_name.git/': Received HTTP code 501 from proxy after CONNECT
不明白是什么问题。我正在从 bitbucket 存储库 web 复制 git clone 命令。我也设置了 git http.proxy 但是没用。
如果需要更多信息，请告诉我。
谢谢
显然，您的代理不支持 HTTP CONNECT tunneling，这就是它以 HTTP 501 (Not implemented) 代码响应的原因：
HTTP CONNECT tunneling
A variation of HTTP tunneling when behind an HTTP Proxy Server is to use the "CONNECT" HTTP method.
In this mechanism, the client asks an HTTP Proxy server to forward the TCP connecting to the desired destination. The server then proceeds to make the connection on behalf of the client. Once the connection has been established by the server, the Proxy server continues to proxy the TCP stream to and from the client. Note that only the initial connection request is HTTP - after that, the server simply proxies the established TCP connection.
This mechanism is how a client behind an HTTP proxy can access websites using SSL (i.e. HTTPS).
Not all HTTP Proxy Servers support this feature, and even those that do, may limit the behaviour (for example only allowing connections to the default HTTPS port 443, or blocking traffic which doesn't appear to be SSL).