I’ve got a web services app that is pointing to an internal resource, but is outside the scope of our configured Dhttps.nonProxyHosts in the tomcat config.
Is there a flag in the app definition that can ‘ignore’ the configured proxy? I’d rather not have to go to all my hosts and modify the tomcat config for this (and future cases). It would be nice to just deploy this and have IIQ honor the preference at the app level. I looked at the documentation, and didn’t see anything that explicitly says ‘proxy off’:
I tried setting https.proxyHost and https.proxyPort to empty strings in the application definition, but no luck.
Any thoughts? Or any other ideas to accomplish what I’m looking to do?
thanks - unfortunately this didn’t bypass the tomcat config on the server itself. For scalability, we’ll likely just have to distribute a config env file that sets the JAVA_OPTS to the values we need.