MID Server Proxy - Specific Endpoints

[stevevandermeer]

Hi All,  I am aware of the configuration to enabled ALL traffic from a MID server to go via a proxy:

How to make MID Server use a proxy for all traffic - Support and Troubleshooting (servicenow.com)

My question is, is there a way to only force traffic for a number of endpoints on a particular MID server to go via the proxy without affecting traffic from the same MID server for all other endpoints ?  

[Slava Savitsky]

I don't think so. The simplest solution would be to set up two MID servers, with one of them using a proxy and the other one not, and have your integrations use the appropriate one.

[stevevandermeer]

Yes, that was my thoughts as well, I was trying to avoid deploying another MID for such a small subset of endpoints.

[Pratiksha]

Nope, you will need two mid server for this. 

[Chambbe]

It looks like you’re trying to configure specific proxy endpoints for your MID Server, and the key point is that MID Servers don’t support granular proxy settings for each protocol. It’s all or nothing:

You set the HTTP or HTTPS proxy in the MID Server config file (config.xml).

That proxy setting applies to every outbound connection the MID Server makes—flows, discovery, integrations, etc.

There’s no way to assign different proxies for different systems or protocols.

So if you need to use different proxy endpoints, you’ll have to:

Use separate MID Servers—each configured with its own proxy.

Or place a reverse proxy in front that routes outbound requests intelligently after they leave the MID Server.

In short, there’s no per-endpoint proxy in MID Server—only global, system-level proxy settings. If you're considering efficient routing or need broader address space, using an IPv6 proxy might help simplify things.