no_proxy option

[eschwartz@…]

I need to use a proxy for external http connections, but not for internal ones. Our proxy blocks access to any internal sites. Normally this works fine because I can set the no_proxy option for any local sites, but bitlbee doesn't seem to have such an option.

[Edward J. Schwartz <eschwartz@…>]

I started working on a patch for this but ran into a complication. It seems that libpurple does not support no_proxy settings. We could work around this by making no_proxy an account level option. Any thoughts?

[wilmer]

Will account-level actually work though? If you do this in proxy.c, it's not even going to have user connection context. :-(

[anonymous]

It works for purple connections:

​https://github.com/bitlbee/bitlbee/pull/144

[ikwyl6]

This would be great for non-libpurple outgoing connections as well. I see in bitlbee.conf there are proxy/socks options for this but I don't want to put my user/pass in a conf file even with proper read/write permissions.

And it would also be great to add this proxy functionality to weechat's ${sec.data} fields to grab these user/pass fields as well instead of inserting them into conf file.