On Fri, 7 Dec 2001, GOMEZ Henri wrote:
Caution, caution with security.
On many sites, the web-server is located on a DMZ so subject
to be hacked, while the Tomcats are behind firewall. Having
webapp (program) could raise many problems.
Hmm... I hope sandboxing is used for tomcat in this
To clarify - this is not a replacement or an 'exclusive' mechanism.
The 'ajp14' based config, where tomcat sends notifications to apache
remains.
Seems like I was reinventing the wheel there for a while. So
AJP14 knows
how configure itself from the running Tomcat... Pretty cool in my book!
Seems like I was reinventing the wheel there for a while. So
AJP14 knows
how configure itself from the running Tomcat... Pretty cool
in my book!
Yes, Henri has added quite a bit of code for that. I did few changes to
make the 'autoconf' usable with other workers and more 'exposed' - see
[EMAIL PROTECTED] wrote:
Yes, Henri has added quite a bit of code for that. I did few changes to
make the 'autoconf' usable with other workers and more 'exposed' - see
jk_webapp, jk_uriEnv.
And this will remain and will be enhanced - we want tomcat to be able to
send notifications like
[EMAIL PROTECTED] wrote:
Please reply - this is an important change !
I would like to add another configuration mechanism for jk2.
If people agree, this should be the default.
Assumptions:
- All webapplication that will be served must be
deployed on the machine running the web server
To clarify - this is not a replacement or an 'exclusive' mechanism.
The 'ajp14' based config, where tomcat sends notifications to apache
remains.
The problems with 'tomcat sending config info to apache' ( and why I
would not make that the 'default' simple config ):
1. It requires a strict
On Fri, 7 Dec 2001, GOMEZ Henri wrote:
Caution, caution with security.
On many sites, the web-server is located on a DMZ so subject
to be hacked, while the Tomcats are behind firewall. Having
webapp (program) could raise many problems.
Hmm... I hope sandboxing is used for tomcat in this
[EMAIL PROTECTED] wrote:
To clarify - this is not a replacement or an 'exclusive' mechanism.
The 'ajp14' based config, where tomcat sends notifications to apache
remains.
Seems like I was reinventing the wheel there for a while. So AJP14 knows
how configure itself from the running Tomcat...
On Sat, 8 Dec 2001, Bojan Smojver wrote:
[EMAIL PROTECTED] wrote:
To clarify - this is not a replacement or an 'exclusive' mechanism.
The 'ajp14' based config, where tomcat sends notifications to apache
remains.
Seems like I was reinventing the wheel there for a while. So AJP14 knows
Please reply - this is an important change !
I would like to add another configuration mechanism for jk2.
If people agree, this should be the default.
Assumptions:
- All webapplication that will be served must be
deployed on the machine running the web server (
otherwise the server can't find
:
Subject: JK2: Configuration(1)
Please reply - this is an important change !
I would like to add another configuration mechanism for jk2.
If people agree, this should be the default.
Assumptions:
- All webapplication that will be served must be
deployed on the machine running the web server
11 matches
Mail list logo
