
Hands on Rub a Chrome Proxy Plugin
Recently, there are always brothers asked how to drum up their own Chrome proxy plug-ins, this thing is difficult to say is not difficult, the key to find the right way. We take ipipgo today as an example of proxy services, teaching you to start from scratch to get a plug-in can actually be used up to ensure that you can get started after reading.
Preparatory actions before plug-in development
First you have to install a Chromedeveloper mode(Don't panic, it's just a few mouse clicks). Open the chrome://extensions page and turn the developer mode switch on in the top right corner. Make a new folder, there must be two files in it:manifest.jsonrespond in singingbackground.jsThe manifest file is the equivalent of an ID card and has to be written that way:
{
"manifest_version": 3,
"name": "IPIPGO Proxy Assistant",
"version": "1.0",
"background": {
"service_worker": "background.js"
},
"permissions": ["proxy", "storage"]
}
Core code for agent configuration
Here's the point! Messing around in background.js. Let's say we use ipipgo's Socks5 proxy and the code looks like this:
chrome.proxy.settings.set({
scope: 'regular',
value: {
mode: 'fixed_servers', {
rules: {
singleProxy: {
scheme: 'socks5', / / / / / / / / / / / / / /
host: 'gateway.ipipgo.com', //insert actual proxy address here
port: 1080
}
}
}
}).
Be careful to change the host to the address of the proxy server you applied for. ipipgo users can see the exclusive configuration information in the console. If you use a dynamic residential proxy, remember to update the IP pool every hour.
Troublesome maneuvers in the real world
I've encountered a lot of brothers complaining about the slow speed of the agent, here to teach you a trick: in the plug-in to add aIntelligent SwitchingFunction. Use ipipgo's API to get the latest node, auto speed test it and cut to the fastest one. Code snippet example:
// Get the list of ipipgo nodes
fetch('https://api.ipipgo.com/nodes')
.then(response => response.json())
.then(nodes => {
nodes.sort((a,b) => a.ping - b.ping);
chrome.storage.local.set({ bestNode: nodes[0] });
});
A Guide to Avoiding the Pit (Lessons Learned Through Tears)
1. Never write a dead proxy account password in the plugin! We recommend using ipipgo'sAPI token authenticationIt's safe and convenient.
2. If the proxy suddenly fails, add an automatic retry mechanism, and set the interval to 3-5 seconds.
3. If you are doing enterprise applications, you should go directly to ipipgo.TK LineThe static residential IP is 35 bucks a month and it's very stable.
Frequently Asked Questions QA
Q: The plugin is installed but can't connect to the agent?
A: First check three points: 1. proxy protocol is not right (HTTP/Socks5 do not confuse) 2. port is not blocked by the fire 3. account balance is adequate
Q: What if I need to manage multiple agents at the same time?
A: Recommended for ipipgoClient Tools, supports batch import of configurations. If you develop by yourself, you can get a configuration table and refer to this data structure:
const proxyList = [
{ region: 'us', type: 'dynamic', server: 'us01.ipipgo.com' },
{ region: 'jp', type: 'static', server: 'jp-static.ipipgo.com' }
];
Why ipipgo?
Having personally tested seven or eight proxy services, there are just three reasons why ipipgo finally locks up:
1. It's so affordable.: Dynamic proxy 7 more than 1 G, do crawler project can save half the cost of
2. Full coverage of agreements: Support from HTTP to Socks5, interfacing with various systems is no problem!
3. Dedicated customer service givesLast time I encountered a cold country agent problem, the technical guy directly 1v1 to get a customized solution!
They recently came out with a newCloud Server + ProxyThe packaged solution, do overseas business brothers can go to see, than buy a separate server and then with a proxy cost-effective a lot.

