1 apache 2.0.52 server
1 tomcat 6.0.18 server running on the same box on port 18080.
a requests come in to the apache server via a load balancer as follows
web browser -> port 80 - >load balancer ->lb redirects and handles 443 processing -> load balancer redirects (or sends) 80 traffic to the actual apache server.
apache server will then proxy to tomcat(localhost).. tomcat does some stuff, and sends it all back up the chain.
The issue I'm having is with the proxypass statements. The url names I'm dealing with change sometimes within each webapp.. like..
as I said before though.. the browser is always https, but the load balancer does all of the 443 processing, so as far as the appserver/tomcat are concerned, they just need to work on 80/18080 (i changed the port myself).
I need to come up with a modular proxypass statement, or some other alternative to allow flexibility to accomodate the 3 situations above.
mod_jk does not use port 8080 (default) for requests from Apache. It uses a separate proxy port (8009 by default) and a special inter-server protocol protocol (ajp). It also has load balancing capabilities of its own so that one Apache can front multiple Tomcats in a cluster.
The newer proxy module does something similar.
"privilege" comes from the Latin words for "private" and "law" (legal) and dates to feudal times. To "claim privilege" meant that you were above the laws that applied to the common people.
posted 10 years ago
I'm not trying to get load balancing/clustering working in apache or tomcat. While there are 2 tomcats running on the same box, neither serve the same applications.
tomcat 5.5 - 8080
tomcat 6.0.18 - 18080
im using mod_proxy, not mod_jk. I guess more of what I need to figure out is how to do wildcard type functionality with mod_proxy/proxypass to be able to get some fancy proxying going on.
posted 10 years ago
I've gotten much further, and I think now my need has changed. Below is the config I'm working with, and now essentially all I need to figure out is how to get /discovery-warranty to always be in the URL, regardless of what someone clicks on, until they go to another location.
For example. http://www.domain.com/discovery-warranty this needs to be authenticated with a /location directive.
there will be other /discovery-somethings that will be authenticated with a /location directive.
We have a load balancer that checks for www.domain.com/discovery-somethings and if it receives a request for www.domain.com/somethingNotDiscovery it will redirect to a main login page... so I need to make sure for each proxy statement, the url is modified/or maintained to always have discovery-something as the first part(or complete) uri, regardless of what someone clicks on while they are in a particular proxied app.
# Proxy back to tomcat
Options -FollowSymLinks -Indexes
Deny from all
Allow from env=BYPASS_AUTH