How to submit a project using a proxy for git
When using Git for version control, it may sometimes be necessary to access remote repositories through a proxy server, especially in the internal network of the company or in certain areas. Here are some basic steps and commands for configuring Git to use the proxy:
Global configuration agent
Set HTTP proxy:
1
git config --global http.proxy http://<username>:<password>@<proxy-server-url>:<port>
Or, if your proxy requires HTTPS:
1
git config --global https.proxy https://<username>:<password>@<proxy-server-url>:<port>
Cancel proxy settings:
1
2git config --global --unset http.proxy
git config --global --unset https.proxy
Project level configuration agent
If you only want to set up a proxy for a specific project, you can omit the --global flag, so that setting will only affect the current project.
Temporary use of proxy
If you don’t want to set up a proxy globally or at the project level, you can also specify a proxy temporarily when executing Git commands:
1 | git -c http.proxy=http://<username>:<password>@<proxy-server-url>:<port> <command> |
Environment variables
Another way to configure the proxy is by setting environment variables:
1 | export HTTP_PROXY=http://<username>:<password>@<proxy-server-url>:<port> |
Notes
- Make sure to replace
<username>,<password>,<proxy-server-url>, and<port>for your proxy server’s actual information. - If your proxy server does not require a username and password, you can omit these parts.
- Some proxy servers may not support directly including usernames and passwords in URLs, in which case you may need to use other tools such as
cURLto set up the proxy. - Make sure your proxy server allows Git to operate the required ports (usually 9418).
After configuring the proxy, you can use Git commands to push and pull code as usual. If you encounter any issues, check that the proxy configuration is correct and make sure that your network connection is not problematic.