Am 17.01.2015 um 03:43 schrieb Chris Arnold:
No JkMount?
mod_jk uses the JkMount directive to decide, which >>requests should be
forwarded. Something like
JkMount /myapp|/* balancer
The directive should be put into the VirtualHost that is >>used in your
Apache web server config to serve the requests for >>/myapp.
When i look at the existing server that works, i cant tell if we are using
mod_proxy or mod_jk. In the SSL-virtualhost, i see:
#This rewrites https://share.anydomain.tld to our share server
RewriteEngine On
RewriteCond %{HTTP_HOST} ^share\.
RewriteCond %{HTTPS} on
RewriteCond %{REQUEST_URI} !^/share/
RewriteRule ^/(.*) https://share.domain.tld:8443/share/ [P]
That will forward any https request with a URI *not* starting with
/share/ using mod_proxy. If there are no ProxyPass directives, it will
not use persistent backend connections though.
JkMount /share/* worker1
And this will use a worker named worker1 to forward anything with a URI
starting with /share/ using mod_jk.
Neither will work as long as your request don't actually hit the Apache
web server.
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
