Thanks for the suggestion Joseph, but in our use case, APIs are already Live and to use fragments or encapsulated assertions, we anyways have to modify the API endpoint to use that fragment. That's why we are looking for some global setting to enable proxy for outbound traffic which can avoid code changes.
Original Message:
Sent: Feb 04, 2025 05:32 PM
From: Joseph Fry
Subject: Enable HTTP Proxy for outbound connections from CA API Gateway
Shubha,
I like the idea of being able to centrally manage some routing settings like this, and I would take it one step further and have "routing templates". So instead of just setting global values, you can create templates that you then choose from in your routing assertions. Because you may not want ALL of your traffic using a proxy or the same set of ciphers.
But then I realized that you can already do that today by using fragments or encapsulated assertions.
So you might consider wrapping your routing assertions inside of one or more encapsulated assertions, then you only have to make updates in one location, but maintain the flexibility to use different settings for different targets.
Original Message:
Sent: Feb 04, 2025 12:03 PM
From: Ben Urbanski
Subject: Enable HTTP Proxy for outbound connections from CA API Gateway
Hello, Shubha. There is not time to include such an enhancement in 11.1.2 which is currently planned for end of March (subject to change). I have added it to the backlog, but based on other priorities, if we pick it up it would likely be post 11.2 in October (also subject to change). In the meantime, you might want to also submit your idea to the community ideas portal for upvoting by other customers.
------------------------------
Ben Urbanski
Product Manager, API Gateway
Layer7 API Management
Original Message:
Sent: Jan 31, 2025 03:07 AM
From: Shubha Shree
Subject: Enable HTTP Proxy for outbound connections from CA API Gateway
I can see in other thread where they are adding an enhancement in 11.1.2 for a similar kind of requirement.
Posting that reply here- "We're adding an enhancement in 11.1.2 to allow customers to set default cipher lists for inbound and/or outbound TLS globally via cluster-wide properties. Until then, you can open a support case to request a hotfix with similar behavior."
Can we incorporate this requirement as well where we can set global proxy for http routing assertion so that all outbound traffic can go via proxy and we don't have to change individual endpoints or policies.
Original Message:
Sent: Jan 28, 2025 03:23 AM
From: Srinivas.Uppoju
Subject: Enable HTTP Proxy for outbound connections from CA API Gateway
We don't have any global proxy option for Http Routing Assertion
Original Message:
Sent: Jan 24, 2025 05:51 AM
From: Shubha Shree
Subject: Enable HTTP Proxy for outbound connections from CA API Gateway
Hi,
How can we enable http proxy for all outbound connections in CA API Gateway 11.1.1 at global level (i.e in form of cluster or system property, env variable or java argument etc) instead of changing each endpoint to enable proxy for outbound connectivity?