On Aug 16, 2013, at 4:14 PM, Marko Asplund <marko.aspl...@gmail.com> wrote:
> Hi, > > We're developing webapps running on Tomcat 7. The apps use third-party > components that we can't modify and those components connect to external > sites using HTTP. > Our ops guys have a policy of routing all outbound traffic through an > authenticating HTTP proxy. > This is a bit of problem for us since the Oracle Java 7 JVM doesn't support > configuring proxy authentication on the JVM level (using e.g. system > properties). > > One possible workaround I could think of is to create a custom javaagent > that would set a default java.net.Authenticator in premain() method. This > approach appears to work in a command line program that > uses HttpURLConnection, but are there any potential caveats to this method > when used with webapps running in Tomcat? One shortcoming is that the same > Authenticator would be used for all webapps in the JVM, but this is > something we can live with. How about a ServletContextListener? http://docs.oracle.com/javaee/6/api/javax/servlet/ServletContextListener.html or a LifecycleListener? https://tomcat.apache.org/tomcat-7.0-doc/config/listeners.html Either one should allow you to configure your proxy settings before your applications start. Dan > > > marko --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
