Add option to exclude ip/hostname from proxy#3000
Add option to exclude ip/hostname from proxy#3000corest wants to merge 1 commit intoblacklanternsecurity:3.0from
Conversation
|
@corest thanks for the PR, this is a good feature to have. This is pretty well implemented except for two things:
Let me know if you want to make an update, otherwise we can do it but it may take a little longer. |
|
All contributors have signed the CLA ✍️ ✅ |
|
I have read the CLA Document and I hereby sign the CLA |
|
recheck |
|
@TheTechromancer thx for a quick feedback. I updated PR addressing both comments:
|
|
before we get too deep, this is still targeting stable - with 3.0 release coming soon (hopefully) if we dont rebase to 3.0 now this will just create more work later. I'm going to go ahead and change the base, you might get some conflicts... sorry @TheTechromancer unless you think there's another 2.x.x release you want to stick this on? |
Use radixtarget library for proxy exclusion lookups, consistent with how targets and blacklists are handled. Supports hostnames, IPs, CIDRs, and NO_PROXY conventions (*.domain, .domain, wildcard *). - Add http_proxy_exclude config and --no-proxy CLI arg - Export NO_PROXY environment variable for external tools - Add tests for proxy exclusion and passthrough behavior
9aef925 to
ae864c6
Compare
|
@corest thanks for the updates; tests look good. We're currently replacing our web library so this will be merged as soon as that's done. |
Motivation for this change is very simple.
I have internal Elasticsearch, that I use as http output destination in presets.
When I use web proxy to access some of targets from different locations, I run into issue, that bbot can't write results into Elasticsearch because it tries to go via proxy.
This configuration option adds possibility to exclude listed endpoints from going via proxy.
Most of code is written by Claude. I'll gladly address any comments on how to improve this. Sorry in advance, if change doesn't follow some of contribution rules.