AAP 2.5 - Proxy settings do not support CIDR notation (/24) in NO_PROXY

Get Help
, , , ,
1

I am trying to define proxy setting in the extra environmental variables in Job settings like below

NO_PROXY = { 
    "HTTPS_PROXY": "http://proxy.example.com:3128",
    "HTTP_PROXY": "http://proxy.example.com:3128",
    "NO_PROXY": "127.0.0.1,localhost,.example.com, 172.20.0.0/24" 
}

AAP doesn’t recognize the “/24” format; instead, if I define individual IP addresses, it works fine.

Is it not supported in AAP 2.5, or did I do anything wrong in this context?

Thanks

2

Probably not what you wanted to hear, but NO_PROXY does not generally support anything but domains/hostnames, domain/hostname wildcards and full IP.

It is also limited by whatever size limitation exists either on OS level or application level for permitted lenght of variables and their content.

We need to talk: Can we standardize NO_PROXY? while a few years old now gives a good primer on the limitations and frustrations that is NO_PROXY.

So you really need to know what underlying library will be using the NO_PROXY env, and on top of it, wildcards do not work on IP’s as standard, and there is no feasible way to fit RFC1819 IP’s explicitly within NO_PROXY
All of RFC1819 would take somewhere around 279160KB (~272MB) and the common limits if memory serves is 128KB or 256KB.

The only feasible way is to avoid using IP’s and rather use hostnames which do allow sane NO_PROXY wildcards unless you know that NO_PROXY will be used in curl, wget or any other tool that is a new enough version to support CIDR.