Import proxies

[akang1937]

Now only a one input proxy ip, so efficiency is too low, a lot of trouble. If you can bulk import proxy ip, it will be very convenient and powerful. On this basis, if we can allocate the bulk proxy ip to each container, it would be great.

[bekh6ex]

I've started working on import from other formats (e.g. FoxyProxy), but didn't finish.

Is that what you asking for or more like importing from proxy_list.txt like file?

If later, then can you describe your use-case in more detail, so we can find a better UI/UX solution together. (i.e. supported format(s), additional user input fields, and what ever might come up)

[jeanjan78]

Yes, importing and exporting as in FoxyProxy would be cool. In FoxyProxy, you can import by pasting some text in a box.

Simple format : ip:port:username:password Complete format : protocol://username:password@server:port?color=00ff00&title=some%20title&proxyDns=false&enabed=false&countryCode=DE&country=Germany&patternIncludesAll=false&patternExcludesIntranet=false

source : https://github.com/foxyproxy/firefox-extension/wiki/Import-Proxy-List

And importing/exporting FoxyProxy json export file would be cool too.

Thanks

[x254724521]

very cool function.

[kurosiger]

+

[msvprogs]

@akang1937 @jeanjan78 @x254724521 @kurosiger Hello,

As a workaround, it's possible to do this from browser console opened in the extension configuration window:

await browser.storage.local.set(<object>)

Where object may be one of the following:

1. Proxy list:

   {
   proxies: [{
     doNotProxyLocal: true,
     host: "hostname",
     id: "83261ff2-72d5-4bac-bdad-776929a0316c",
     password: "b",
     port: 9161,
     title: "proxy name",
     type: "http",
     username: "a"
   },
   ...,
   ...
   ]
   }

2. Container-proxy relation list (container is identified by numeric index):

   {
   relations: {
   
   "firefox-container-1": ["proxy-1-uuid"],
   "firefox-container-2": ["proxy-2-uuid"],
   ...
   "firefox-container-N": ["proxy-N-uuid"]
   }
   }