Three recent questions on Tomcat Convertors
Archive - Originally posted on "The Horse's Mouth" - 2009-07-07 08:36:15 - Graham EllisCan mod_proxy receive a request in one protocol and forward it in another?
mod_proxy (in httpd 2.2.x at least) is capable of protocol conversion - at least from http to ajp. https to http, and https to ajp should also work. mod_proxy_connect provides the capability of onward connection via https according to the manual. It is not a facility I have used personally, as the requirement for a secure connection between two local machines on the same subnet is not common when compared to external secure connections. See:
http://httpd.apache.org/docs/2.2/mod/mod_proxy.html
What is ajp 1.4 protocol?
I have taken a look at "ajp 1.4 protocol". The commonly used protocol / current standard is 1.3, but there are a (very few references around to 1.4. As an educated guess, the 1.4 proposal which included some sort of negotiated content system, was dropped.
The Tomcat project page includes details of the ajp 1.3 protocol:
http://tomcat.apache.org/connectors-doc/ajp/ajpv13a.html
but there are no similar pages for ajp 1.4 - see:
http://tomcat.apache.org/connectors-doc/
What is the "accept count" on a connector, what is its default value, and what should I set it to?
According to the documentation, the default acceptcount (the number of connections that can be help waiting in a queue) is 10. Usual recommendation is that the acceptCount be set to the same value as the maximum connections to allow for there to be one connection waiting for each one being processed, although with the throttling at the httpd rather than the tomcat level in most installations, this could be a moot point.