#1318 new enhancement

no_proxy option

Reported by: eschwartz@… Owned by:
Priority: minor Milestone:
Component: BitlBee Version: Unspecified
Keywords: Cc:
IRC client+version: Client-independent Operating System: Linux
OS version/distro:


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.

Attachments (0)

Change History (4)

comment:1 Changed at 2020-01-23T16:28:52Z by 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?

comment:2 Changed at 2020-01-26T06:08:04Z by wilmer

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

comment:3 Changed at 2020-04-20T15:59:35Z by anonymous

It works for purple connections:

comment:4 Changed at 2021-06-27T14:25:57Z by 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 ${} fields to grab these user/pass fields as well instead of inserting them into conf file.

Modify Ticket

as new The ticket will remain with no owner.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.