The directive JkOptions allow you to set many forwarding options which will enable (+)
or disable (-) following option.
JkOptions ForwardKeySize, you ask mod_jk, when using ajp13, to forward also the SSL Key Size as
required by Servlet API 2.3.
This flag shouldn't be set when servlet engine is Tomcat 3.2.x (on by default).
JkOptions +ForwardKeySize
JkOptions ForwardURICompat, you ask mod_jk to send the URI to Tomcat normally,
which is less spec compliant but mod_rewrite compatible,
use it for compatibility with Tomcat 3.2.x engines (on by default).
JkOptions +ForwardURICompat
JkOptions ForwardURICompatUnparsed, the forwarded URI
is unparsed, it's spec compliant but broke mod_rewrite.
JkOptions +ForwardURICompatUnparsed
JkOptions ForwardURIEscaped, the forwarded URI is escaped and
Tomcat (since 3.3 rc2) will do the decoding part.
JkOptions +ForwardURIEscaped
JkOptions ForwardDirectories is used in conjunction with DirectoryIndex
directive of Apache web server. As such mod_dir should be available to Apache,
statically or dynamically (DSO)
When DirectoryIndex is configured, Apache will create sub-requests for
each of the local-url's specified in the directive, to determine if there is a
local file that matches (this is done by stat-ing the file).
If ForwardDirectories is set to false (default) and Apache doesn't find any
files that match, Apache will serve the content of the directory (if directive
Options specifies Indexes for that directory) or a 403 Forbidden response (if
directive Options doesn't specify Indexes for that directory).
If ForwarDirectories is set to true and Apache doesn't find any files that
match, the request will be forwarded to Tomcat for resolution. This is used in
cases when Apache cannot see the index files on the file system for various
reasons: Tomcat is running on a different machine, the JSP file has been
precompiled etc.
Note that locally visible files will take precedence over the
ones visible only to Tomcat (i.e. if Apache can see the file, that's the one
that's going to get served). This is important if there is more then one type of
file that Tomcat normally serves - for instance Velocity pages and JSP pages.
JkOptions +ForwardDirectories
JkOptions ForwardLocalAddress, you ask mod_jk to send the local address,
of the Apache web server instead remote client address. This can be used by
Tomcat remote address valve for allowing connections only from registered Apache
web servers.
JkOptions +ForwardLocalAddress
JkOptions FlushPackets, you ask mod_jk to flush Apache's connection
buffer after each AJP packet chunk received from Tomcat. This option can have
a strong performance penalty for Apache and Tomcat as writes are performed
more often than would normally be required (ie: at the end of each
response).
JkOptions DisableReuse, you ask mod_jk to close connections immediately
after their use. Normally mod_jk uses persistent connections and pools idle
connections to reuse them, when new requests have to be sent to Tomcat.
Using this option will have a strong performance penalty for Apache and Tomcat.
Use this only as a last resort in case of unfixable network problems.
If a firewall between Apache and Tomcat silently kills idle connections,
try to use the worker attribute socket_keepalive in combination with an appropriate
TCP keepalive value in your OS.
The directive JkEnvVar allows you to forward an environment variable from Apache server to Tomcat engine.
The variable can be retrieved on the Tomcat side as a request attribute.
You must add a default value as a second parameter to the directive.
JkEnvVar SSL_CLIENT_V_START undefined