Extension using wrong proxy authentication credentials

[crypt1d]

I have two containers using two different proxy configurations. The configurations differ only by the authentication credentials - ie the connecting proxy host is the same, its just that the username is different.

Unfortunately it seems that the extension will always use the authentication credentials of the first proxy, regardless of how I configure the second one. This can be confirmed by observing the request Authentication headers.

To reproduce:

• Create two containers and two proxy configurations. Each container should use a dedicated proxy configuration
• Set the proxy configs to use the same proxy host (http one, I haven't tested with socks), but make sure that the authenticating user is different
• Make a request through both containers to ipinfo.io
• Observe that the Authentication header is the same in both containers (even though it should be different).

Extension version: 0.1.22