On Tuesday 11 August 2009 10:40:48 Mark Thomas wrote: > Rainer Frey wrote: > > Some customers (with varying degree of experience) want to use this > > behind Apache HTTPD as reverse proxy and ask us for instructions. > > What would you recommend to describe in a general instruction document > > without knowing more details of the customers environment, mod_proxy_http > > or mod_proxy_ajp? (I think mod_jk is an option mostly for knowledgable > > customers who have specific reasons to consider it). > > If the customer has done this before, whatever they are familiar with. > If I had a free choice mod_proxy_http.
Thanks for this input. Do you have any technical reasons, or is it more about maturity of the module? > > With AJP, > > isn't that information also available in the protocol request and set > > automatically by the AJP connector? > > I believe so. I tried, and it works. Does it make sense to set these attributes at all on an APR connector then? > > I also have an idea for a (maybe dirty) hack: if I always put the > > proxyName and proxyPort attributes in server.xml, and use properties that > > expand to empty values by default, will this work in case there is no > > proxy in the setup? > > Have you tried it? I did now, and it does work. I noticed that property expansion in server.xml seems not to be documented at all. Is this intentionally left out, or just missing? Also, properties from catalina.properties and from Java System Properties are expanded, but it seems that catalina.properties takes precedence. I find this surprising, because system properties are in my perception more dynamic and runtime/individual start specific than values in a config file. Is this intentional behavior? If not, should I report a bug? > Mark Rainer --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
