
What does this thing do? You'll see.
We developers often need to debug interfaces, and when we run tests locally, we always need to connect to various services, right? If you leave the global proxy on, all localhost requests will be hijacked by the proxy, and the result will beI can't even access my own computer's services.The following is an example of a proxy blocking a curl request. For example, you local machine started a MySQL service on port 3306, this time curl request will be intercepted by the proxy, you say angry?
This is where the noproxy option is a lifesaver! It can tell curl: "These addresses don't need to go through the proxy, access them directly". This feature is especially suitable for ipipgo proxy service partners, both can enjoy high quality proxy, but does not affect the local development.
Hands-on with noproxy setup
The setup is as simple as it gets, in two poses:
Temporary setup (recommended)
curl --noproxy "localhost,127.0.0.1,192.168." http://你的内网地址
Permanent setup (for lazy people)
export no_proxy="localhost,127.0.0.1,.example.com"
Watch out for a few pit stops:
- domain name preceded byEnglish period (punct.)Can match subdomains (e.g. .example.com can match a.example.com)
- expense or outlaywildcard character (computing)Be careful, different systems have different levels of support
- Multiple addresses withEnglish commaSeparate them. Never use Chinese symbols.
Practical cases to go a wave
Suppose we use ipipgo's proxy service to access both the public API and local services:
Accessing the public network with a proxy
curl -x http://user:pass@proxy.ipipgo.com:8080 https://public-api.com
Bypassing proxy to access local
curl --noproxy "localhost" http://127.0.0.1:3000/api
Mixed use scenarios
export no_proxy="localhost,internal.company.com"
curl -x http://proxy.ipipgo.com:8080 https://both.com
With this setup, local development environments and intranet systems are accessible, and public requests go to ipipgo's premium proxy for the best of both worlds!
Common Rollover Scene QA
| Symptoms of the problem | method settle an issue |
|---|---|
| Setting up noproxy or going proxy | Check environment variable naming (no_proxy not NO_PROXY) |
| wildcards do not take effect | Change to match with a domain prefix (e.g. .example.com) |
| Some subdomains are missing | Adding parent and child domains to the list |
Why ipipgo?
After using seven or eight proxy services, I ended up using ipipgo for the long term for three reasons:
- Connection is steady as an old dog, never had a proxy drop out in the middle of a session.
- be in favor ofWhitelisting/IP BindingSecurity is guaranteed.
- Customer service response is fast, the last 3:00 a.m. to mention the work order actually seconds back!
Especially theirs.Dynamic Residential AgentsThe success rate when doing data collection can go up to 98%, with noproxy settings simply unbeatable. Recently, the new user registration also sends 5G flow, not gripping white not gripping.
Cold Tips
Many people don't realize that noproxy can be played this way:
- Setting up in a Docker container
--network host+noproxy to solve container networking problems - When using Postman, put the no_proxy environment variable in the settings.
- expense or outlay
curl --noproxy ''Temporarily disable all proxies (use with caution)
Finally, a true story: a brother set up noproxy but forgot to restart the terminal, the result of troubleshooting for three hours. So after you change the environment variable, remember toOpen a new terminal window.Ah old iron!

