- Mark as New
- Subscribe to RSS Feed
- Permalink
‎16 Mar 2023
05:26 PM
- last edited on
‎12 May 2023
09:54 AM
by
Michal_Gebacki
I have been trying to get an extension I'm developing to use the proxy defined in the ActiveGate configuration.
But the use of requests tries to connect directly to the URL. I can catch that because I'm dumping traffic and confirming it's not going through a proxy.
Of course, I can get requests to use a proxy, but just wondering if I didn't get this wrong.
Solved! Go to Solution.
- Labels:
-
activegate
-
extensions
-
python
- Mark as New
- Subscribe to RSS Feed
- Permalink
‎16 Mar 2023 05:30 PM
You are doing it correctly. The requests library used is completely standalone from the AG configuration. You’ll have to implement it separately.
we’re looking into ways of improving this in Extensions Framework 2.0, but there is no commitment yet.
Mike
- Mark as New
- Subscribe to RSS Feed
- Permalink
‎07 Mar 2024 02:59 PM
Hi @Mike_L ,
I just came accross this situation as well for a provided Extension 2.0 (Confluent Kafka). It would run on an AG that is only allowed to communicate via proxy. However the extension doesn't have the option to configure a proxy. Neither does the EF2 use the system-wide proxy set?
What would be the option here, then?
Cheers!
- Mark as New
- Subscribe to RSS Feed
- Permalink
‎07 Mar 2024 04:35 PM
It's been raised a few times over the past year with the team responsible for the Prometheus data source, but it didn't get a high enough priority to add it. I'll point the PM to this conversation for further proof.
