Hi, server.xml
<Connector port="8009" enableLookups="false" connectionTimeout="20000" protocol="AJP/1.3" redirectPort="8443" /> <Connector port="8010" protocol="AJP/1.3" secure="true" scheme="https" enableLookups="false" connectionTimeout="20000" /> <Engine name="Catalina" defaultHost="localhost" jvmRoute="*tomsrv02*"> worker.properties worker.*tomsrv02*.type=ajp13 worker.*tomsrv02*.host=172.17.1.45 worker.*tomsrv02*.port=8009 worker.*tomsrv02*.lbfactor=1 worker.*tomsrv02*.connection_pool_timeout=20 worker.tomsrv02sec.type=ajp13 worker.tomsrv02sec.host=172.17.1.45 worker.tomsrv02sec.port=8010 *worker.tomsrv02sec.route=tomsrv02* worker.tomsrv02sec.lbfactor=1 worker.tomsrv02sec.connection_pool_timeout=20 We use two connectors to apply separate rules (e.g. firewall, monitoring tools) for each one of them. Best regards, Robert On Wed, Dec 19, 2012 at 12:03 AM, Bob Myers <b...@nextfort.com> wrote: > > On Dec 18, 2012, at 6:40 PM, Caldarale, Charles R wrote: > > >> From: Bob Myers <b...@nextfort.com> > >> Re: jvmRoute with multiple AJP Connectors for one Engine > > > >>>> <Connector executor="tomcatThreadPool" port="8009" > >>>> protocol="AJP/1.3" redirectPort="443" /> <Connector > >>>> executor="tomcatThreadPool" port="8019" protocol="AJP/1.3" > >>>> scheme="https" secure="true" /> > > > >>> Why bother? > > > >> What do you mean, why bother? > > > > Because the AJP <Connector> automatically sets the scheme and secure > attributes when the original request is via SSL. Consequently, you don't > need a separate <Connector> just for that. > > Ok, I missed that. Thanks, that solves it. I had it that way originally > and for some reason I thought it wasn't working without the explicit scheme > and secure attributes. I must have had that wrong. > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
