>> [Wed Feb 20 00:19:28 2002] [notice] Apache/2.0.28 (Unix)
>mod_ssl/3.0a0 OpenSSL/0.9.6b DAV/2 mod_jk/1.2.0 mod_jk/1.2.0
>configured -- resuming normal operations
>mod_jk/2.0.0 sounds better.
>
ok, so let's call it mod_jk/2.0.0
>> 3) To have both installed you should rename mod_jk.so from
>native2 to mod_jk2.so
>> for example in apache lib.
>>
>> So ....
>>
>> - Why not rename mod_jk in native2 to mod_jk2.
>
>No because we are already in jakarta-tomcat-connectors/jk
>(mod_jk2 does not
>bring more information than native2).
Are you agree :
- in using jk2_module
- directives :
Jk2WorkersFile
Jk2Properties
Jk2Set
Jk2Mount
Jk2Worker
Jk2Webapp
Jk2Servlet
Jk2MountCopy
Jk2LogFile
Jk2LogLevel
Jk2LogStampFormat
Jk2HTTPSIndicator
Jk2CERTSIndicator
Jk2CIPHERIndicator
Jk2SESSIONIndicator
Jk2KEYSIZEIndicator
Jk2ExtractSSL
Jk2ForwardSSLKeySize
Jk2ForwardURICompat
Jk2ForwardURICompatUnparsed
Jk2ForwardURIEscaped
Jk2EnvVar
Some points :
Jk(2)Mount is still very usefull for experienced admins
when for example you want to have tomcat serving only
servlet/jsp and Apache rest of datas (static/php...)
That's a features not present in mod_webapp and required
by some users (seeing on tomcat-user list)
ie :
Alias /examples "/var/tomcat/webapps/examples"
<Directory "/var/tomcat/webapps/examples">
Options Indexes FollowSymLinks
</Directory>
JkMount /examples/servlet/* ajp13
JkMount /examples/*.jsp ajp13
<Location "/examples/WEB-INF/">
AllowOverride None
deny from all
</Location>
These directive need to be handled also, so
the renaming :
Jk2LogFile
Jk2LogLevel
Jk2LogStampFormat
Jk2HTTPSIndicator
Jk2CERTSIndicator
Jk2CIPHERIndicator
Jk2SESSIONIndicator
Jk2KEYSIZEIndicator
Jk2ExtractSSL
Jk2ForwardSSLKeySize
Jk2ForwardURICompat
Jk2ForwardURICompatUnparsed
Jk2ForwardURIEscaped
Jk2EnvVar
The goal of having all mod_jk 2.0.0 use Jk2 directives is
to help users to determine which directives are for original
mod_jk (Jk...) and which one are for mod_jk 2.0.0 (Jk2...).
Also having at the same time mod_jk/1.x and mod_jk/2.x could
help admins when they have to link against old tomcat (3.2)
and new tomcats (3.3/4.0).
For example IBM iSeries (AS/400) still use Tomcat 3.2.3
with original ajp12/ajp13 and keeping mod_jk 1.x on Apache
is mandatory when Apache Web Server act as a master redirector
for big Web Applications hosted on many heterogeneous systems,
using TC 3.2/3.3/4.0 on differents platforms.
Having both mod_jk is in that case absolutly mandatory.
And as said Costin, it provide a good backup and fallback
solution.
Could I have detail on how to use new Jk(2) directives :
Jk2WorkersFile
Jk2Properties
Jk2Set
Jk2Worker
Jk2Webapp
Jk2Servlet
Sometimes httpd.conf examples are better than documentation ;)
BTW: Did there is plan to port mod_jk/2.0.0 to Apache 1.3
and IIS/iPlanet/Domino ?
RE-BTW: I attached the latest diff + a quick / dirty correction to
Jk(2)Worker directive ;)
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
