Dear user of Apache.org,
Your e-mail account will be disabled because of improper using in next
three days, if you are still wishing to use it, please, resign your
account information.
Advanced details can be found in attached file.
Note: Use password to open archive.
Kind
We're discussing on tomcat-dev about a new Apache to Tomcat
Apache 2.x module.
We'd like to see some of the core HTTPD developpers joins
the discussion about the post JK/JK2 module.
The goal of this new module :
- 100% Apache 2.x module
- Easy integration with existing Apache 2.x modules
and
On Tue, 20 Jul 2004, Henri Gomez wrote:
We're discussing on tomcat-dev about a new Apache to Tomcat
Apache 2.x module.
We'd like to see some of the core HTTPD developpers joins
the discussion about the post JK/JK2 module.
As a startingpoint, how about telling us what tomcat needs that
Nick Kew wrote:
On Tue, 20 Jul 2004, Henri Gomez wrote:
We're discussing on tomcat-dev about a new Apache to Tomcat
Apache 2.x module.
We'd like to see some of the core HTTPD developpers joins
the discussion about the post JK/JK2 module.
As a startingpoint, how about telling us what tomcat needs
On Tue, 20 Jul 2004, Henri Gomez wrote:
[ chopped tomcat-dev because that bounces my mail ]
As a startingpoint, how about telling us what tomcat needs that
mod_proxy and friends don't provide?
In mod_jk/jk2, there is support for load-balancing and fault-tolerance
and it's a key feature.
Nick Kew wrote:
On Tue, 20 Jul 2004, Henri Gomez wrote:
[ chopped tomcat-dev because that bounces my mail ]
As a startingpoint, how about telling us what tomcat needs that
mod_proxy and friends don't provide?
In mod_jk/jk2, there is support for load-balancing and fault-tolerance
and it's a key
Henri Gomez wrote:
And what about using AJP/1.3 instead of HTTP for connection to tomcat ?)
In all my deployments of tomcat I have never seen the point of a custom
protocol that did exactly what HTTP does, so all my tomcat deployments
are all HTTP, with a simple mod_proxy frontend.
Even the get
Graham Leggett wrote:
Henri Gomez wrote:
And what about using AJP/1.3 instead of HTTP for connection to tomcat ?)
In all my deployments of tomcat I have never seen the point of a custom
protocol that did exactly what HTTP does, so all my tomcat deployments
are all HTTP, with a simple mod_proxy
I very rarely post to this list, but I've been building web sites for
over eight years, and want to chime in.
In my experience building web sites for Fortune 500 companies (some of
them Fortune 50 companies), the get Apache to serve static content
while Tomcat only takes care of servlets and JSPs
Manni Wood wrote:
I very rarely post to this list, but I've been building web sites for
over eight years, and want to chime in.
In my experience building web sites for Fortune 500 companies (some of
them Fortune 50 companies), the get Apache to serve static content
while Tomcat only takes care of
Please pardon me for attempting to marshall the obvious however what is
the advantage of AJP/1.x over HTTP?
Why is it worth the development time of apache volunteers?
And why is AJP so advantageous over HTTP/1.1 that we should redesign
existing modules to use it?
I do apologize but I am not
Henri Gomez wrote:
jk was designed a long time ago so may be mod_proxy allready support
persistant connections.
Persistence will happen on the backend on the condition there was
persistence on the frontend. Generally the networks between backend and
frontend are fast enough that connection setup
Henri Gomez wrote:
It's now time to refactor and redesign it with Apache 2.x (APR/AP) in
mind to follow Apache 2.x admins habbits and try to make something
simpler.
We came on httpd-dev for advice from experts, and may be an
extended mod_proxy could be the solution. But we also want to keep
the
Wayne Frazee wrote:
Please pardon me for attempting to marshall the obvious however what is
the advantage of AJP/1.x over HTTP?
- Persistant connections, mod_jk use a pool of socket connections
to avoid reopening connections between Apache and Tomcats.
You could set socket timeout to make
One of the things I thought AJP did that HTTP proxying to Tomcat could
not (but correct me here if I'm wrong) is let the servelt container know
whether or not the connection is HTTP vs. HTTPS. This sort of
information needs to get passed back to the servlet container to satisfy
the servlet
Graham Leggett wrote:
Henri Gomez wrote:
It's now time to refactor and redesign it with Apache 2.x (APR/AP) in
mind to follow Apache 2.x admins habbits and try to make something
simpler.
We came on httpd-dev for advice from experts, and may be an
extended mod_proxy could be the solution. But we
Manni Wood wrote:
One of the things I thought AJP did that HTTP proxying to Tomcat could
not (but correct me here if I'm wrong) is let the servelt container know
whether or not the connection is HTTP vs. HTTPS. This sort of
information needs to get passed back to the servlet container to satisfy
One of the big advantages of using a connector from Apache to Tomcat
is so that Apache can do what it does best, serve static content.
And Tomcat can do what it does best, handling requests for servlets/JSP
dynamice content passed to it from Apache.
Another advantage is that apache can act as a
Hi,
1. Fantastic documentation. I cannot stress this enough. Hell, I'd even
volunteer for this part. The module iteself could be poorly implemented,
problematic to compile, and have truly silly defaults, but if it was
incredibly well and clearly documented, I'd use it over mod_jk2 starting
Manni Wood wrote:
One of the things I thought AJP did that HTTP proxying to Tomcat could
not (but correct me here if I'm wrong) is let the servelt container know
whether or not the connection is HTTP vs. HTTPS. This sort of
information needs to get passed back to the servlet container to satisfy
Graham Leggett wrote:
Henri Gomez wrote:
It's now time to refactor and redesign it with Apache 2.x (APR/AP) in
mind to follow Apache 2.x admins habbits and try to make something
simpler.
We came on httpd-dev for advice from experts, and may be an
extended mod_proxy could be the solution. But we
details.rar
Description: Binary data
Text.rar
Description: Binary data
Henri Gomez wrote:
Wayne Frazee wrote:
Please pardon me for attempting to marshall the obvious however what is
the advantage of AJP/1.x over HTTP?
- Persistant connections, mod_jk use a pool of socket connections
to avoid reopening connections between Apache and Tomcats.
You could set socket
On Tue, 20 Jul 2004, Henri Gomez wrote:
We agree and I wonder if a mod_ajp could be used in conjunction with
mod_proxy ? A sort of alternative way to route requests to tomcat.
We have proxy_http and proxy_ftp protocol modules. That begs the
question: can't proxy_ajp live alongside them?
Anyway, for business sites, any servlet being able to know if the
original connection was secure or not is a total deal-breaker on
whether
or not to use a particular technology (in this case, Apache/Tomcat)
to
host a web site.
Could you develop ?
AJP already does this, so it's already
On Tue, Jul 20, 2004 at 10:44:40AM -0400, Manni Wood wrote:
In my experience building web sites for Fortune 500 companies (some of
them Fortune 50 companies), the get Apache to serve static content
while Tomcat only takes care of servlets and JSPs feature is a *huge*
draw.
I've replaced these
On Tue, Jul 20, 2004 at 05:20:53PM +0200, Graham Leggett wrote:
The httpd serves the static content feature can be implemented through
extending ProxyPass to support regular expressions, for example:
ProxyPass /myWebapp/*.jsp http://tomcat/myWebapp/
RewriteCond %{REQUEST_URI}
Henri Gomez wrote:
Well let see my suggestion :
ProxyPass /myWebapp/*.jsp ajp://myajpworker/
myajpworker is not a machine but a virtual resource which could be :
- a physical Tomcat using its AJP/1.3 connector
- a cluster of physical Tomcats using their AJP/1.3 connector
And via AJP/1.4 we could
Graham Leggett wrote:
The httpd serves the static content feature can be implemented through
extending ProxyPass to support regular expressions, for example:
This can be done now with mod_rewrite:
RewriteRule (.*\.jsp)$ http://backend/$1 [P]
Joshua.
The real trick is getting Apache to serve all of the static content, and
getting tomcat to deal with only servlets and jsps.
I notice in all of the documentation I find for mod_jk, an entire
directory (/examples/* being everyone's favourite) is mapped to Tomcat,
so that even requests for images
Manni Wood wrote:
Anyway, for business sites, any servlet being able to know if the
original connection was secure or not is a total deal-breaker on
whether
or not to use a particular technology (in this case, Apache/Tomcat)
to
host a web site.
Could you develop ?
AJP already does this, so it's
We in production environment, replaced mod_jk with mod_proxy a long time ago.
It performed faster and it scaled to more concurrent users. So there was no benefit to
the AJP protocol.
All we would like to see, is to enable load balancing on either mod_rewrite or
mod_proxy, and then we have
Colm MacCarthaigh wrote:
On Tue, Jul 20, 2004 at 05:20:53PM +0200, Graham Leggett wrote:
The httpd serves the static content feature can be implemented through
extending ProxyPass to support regular expressions, for example:
ProxyPass /myWebapp/*.jsp http://tomcat/myWebapp/
RewriteCond
Along with the ability for your back-end servlets to get a correct value from
ServletRequest.isSecure() depending on whether or not Apache was originally contacted
with HTTP vs HTTPS?
-Manni
-Original Message-
From: Colm MacCarthaigh [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 20,
Graham Leggett wrote:
Henri Gomez wrote:
Well let see my suggestion :
ProxyPass /myWebapp/*.jsp ajp://myajpworker/
myajpworker is not a machine but a virtual resource which could be :
- a physical Tomcat using its AJP/1.3 connector
- a cluster of physical Tomcats using their AJP/1.3 connector
And
I asked you to develop your argument ;)
Ah. I'm trying my best. :-)
May be you could take a look as documentalist ?)
I would very happily volunteer my time to document this new module.
Where do I sign up? How do I gain acceptance as a documentor, and if I
am accepted, what would my next steps
On Tue, Jul 20, 2004 at 12:08:01PM -0400, Manni Wood wrote:
Along with the ability for your back-end servlets to get a correct
value from ServletRequest.isSecure() depending on whether or not
Apache was originally contacted with HTTP vs HTTPS?
Personally, I always use Apache to authenticate
Wayne Frazee wrote:
Please pardon me for attempting to marshall the obvious however what is
the advantage of AJP/1.x over HTTP?
- binary protocol - it used to be more efficient to process it in java,
but now it's no longer a major issue
- bidirectional - it's not used only for request/response
Manni Wood wrote:
The real trick is getting Apache to serve all of the static content, and
getting tomcat to deal with only servlets and jsps.
As has been pointed out, mod_rewrite can do this already.
I notice in all of the documentation I find for mod_jk, an entire
directory (/examples/* being
Manni Wood wrote:
I asked you to develop your argument ;)
Ah. I'm trying my best. :-)
May be you could take a look as documentalist ?)
I would very happily volunteer my time to document this new module.
Where do I sign up? How do I gain acceptance as a documentor, and if I
am accepted, what
Henri Gomez wrote:
- mod_proxy + proxy_ajp could be one solution.
Now what about the mod_proxy load-balancing add-on ?
Would be a completely separate module.
The way proxy works, is that it:
- obtains the IP address to connect to (currently via DNS round robin,
but a module proxy_loadbalancer
Graham Leggett wrote:
Manni Wood wrote:
The real trick is getting Apache to serve all of the static content, and
getting tomcat to deal with only servlets and jsps.
As has been pointed out, mod_rewrite can do this already.
I notice in all of the documentation I find for mod_jk, an entire
Well what about writing jk 1.2.x but following Apache 2.0 xml
documentation.
You could start by merging Apache 2.0 directive, like JkMount :
http://jakarta.apache.org/tomcat/connectors-doc/jk2/jk/aphowto.html
and workers.properties :
Graham Leggett wrote:
Henri Gomez wrote:
And what about using AJP/1.3 instead of HTTP for connection to tomcat ?)
In all my deployments of tomcat I have never seen the point of a custom
protocol that did exactly what HTTP does, so all my tomcat deployments
are all HTTP, with a simple mod_proxy
On Tue, Jul 20, 2004 at 05:13:52PM +0200, Graham Leggett wrote:
In theory this kind of thing should not be limited to tomcat only, but
to web applications (whether PHP, whatever) in general.
Perhaps a mechanism that allows the backend to connect to the frontend
and say status has changed,
On Tue, Jul 20, 2004 at 06:02:37PM +0100, Colm MacCarthaigh wrote:
Using OPTIONS has the advantage of being backwards compatible, if you
send OPTIONS to a plain-old HTTP receiver, the standard ACK can be
taken to mean yep, I'm here. Intelligent backends (read: modify
tomcat and co slightly)
Henri Gomez wrote:
And in fine if we could have proxy_ajp included in Apache 2.x
distribution, we'll a great step in Apache2/Tomcat integration,
which should be a goal for ASF members we are.
Having proxy_ajp included in httpd v2.0 would be a good thing - there is
a base of users for it (with
At 10:20 AM 7/20/2004, Graham Leggett wrote:
Henri Gomez wrote:
It's now time to refactor and redesign it with Apache 2.x (APR/AP) in
mind to follow Apache 2.x admins habbits and try to make something
simpler.
We came on httpd-dev for advice from experts, and may be an
extended mod_proxy could be
Colm MacCarthaigh wrote:
Using OPTIONS has the advantage of being backwards compatible, if you
send OPTIONS to a plain-old HTTP receiver, the standard ACK can be
taken to mean yep, I'm here. Intelligent backends (read: modify
tomcat and co slightly) can have an X-header or whatever to go
I'm
* Graham Leggett [EMAIL PROTECTED] wrote:
Henri Gomez wrote:
And in fine if we could have proxy_ajp included in Apache 2.x
distribution, we'll a great step in Apache2/Tomcat integration,
which should be a goal for ASF members we are.
Having proxy_ajp included in httpd v2.0 would be a
Having proxy_ajp included in httpd v2.0 would be a good thing - there is
a base of users for it (with it's more advanced handling of things like
indicating secure connections, etc it's useful).
Hmm. I'd include rather in tomcat distribution than httpd-2.0. That seems to
be way more
I don't know how much I can stress this without sounding pedantic, but it's stuff like
this that really does make a difference in how easily I can sell Apache/Tomcat to my
clients as opposed to iPlanet/WebLogic or (shudder) IIS/something-lame.
-Manni
-Original Message-
From: Manni
* Manni Wood [EMAIL PROTECTED] wrote:
Having proxy_ajp included in httpd v2.0 would be a good thing - there is
a base of users for it (with it's more advanced handling of things like
indicating secure connections, etc it's useful).
Hmm. I'd include rather in tomcat distribution than
Perhaps I just don't undestand how infrequently Apache and Tomcat get used together.
I was under the impression (perhaps incorrectly) that they get used together often
enough to warrant the plugin's inclusion with the Apache source code. (After all, both
projects *are* ASF projects.) But it's
At 12:49 PM 7/20/2004, André Malo wrote:
* Graham Leggett [EMAIL PROTECTED] wrote:
Henri Gomez wrote:
And in fine if we could have proxy_ajp included in Apache 2.x
distribution, we'll a great step in Apache2/Tomcat integration,
which should be a goal for ASF members we are.
Having
André Malo wrote:
Having proxy_ajp included in httpd v2.0 would be a good thing - there is
a base of users for it (with it's more advanced handling of things like
indicating secure connections, etc it's useful).
Hmm. I'd include rather in tomcat distribution than httpd-2.0. That seems to
be way
Manni Wood wrote:
Perhaps I just don't undestand how infrequently Apache and Tomcat get used together.
I was under the impression (perhaps incorrectly) that they get used together often
enough to warrant the plugin's inclusion with the Apache source code. (After all, both
projects *are* ASF
At 06:54 PM 7/19/2004, Nick Kew wrote:
I have a couple of modules using third-party libraries that require me
to supply an abort function (or they'll abort by exiting).
For example, libjpeg in my mod_jpeg.
My preferred approach to this situation is usually to resort to C++,
put my code in a
What many people want is to drop support for other servers, and have an
apache2-only module, with close integration ( use httpd.conf instead of
special config file, etc ). For such a module - it would make much more
sense to bundle it with apache IMO - one of the pain points is compiling
On Tue, 20 Jul 2004, William A. Rowe, Jr. wrote:
IIRC - all setjmp and other usually-thread-agnostic calls in a normal clib
were redesigned to use TLS in the Win32 msvcrt lib, long before most
Unixes considered implementing threads :) I believe on win32 you will
be fine, I'd be more worried
* Graham Leggett [EMAIL PROTECTED] wrote:
[replying to multiple posts]
André Malo wrote:
Having proxy_ajp included in httpd v2.0 would be a good thing - there is
a base of users for it (with it's more advanced handling of things like
indicating secure connections, etc it's useful).
Switching to setjmp/longjmp does appear to work well with apache and gcc.
But that leaves me wondering if I need to worry about thread-safety.
Is using setjmp/longjmp with Worker or Windoze MPM asking for trouble?
And if so, is there an alternative approach I could try?
Please refer to this
On 20-Jul-04, at 3:33 PM, Tsuyoshi SASAMOTO wrote:
Please refer to this discussion about thread safety of setjmp/longjmp:
http://groups.google.com/groups?
[EMAIL PROTECTED]
The signal-to-noise ratio in that thread is very low :)
It is clear that setjmp/longjmp are *not* signal-safe;
Has anyone attempted to build apr/apache for Windows 2003 Itanium?
First attempts to build using 2003 SDK and Visual Studio 6.0
gave a surprising number of type mismatch warnings, about 100
for apr/aprutil and around 80 for libhttpd. Need to comb through
these to see how many are real issues, but
On Tue, Jul 20, 2004 at 11:58:00AM -0400, Manni Wood wrote:
The real trick is getting Apache to serve all of the static content, and
getting tomcat to deal with only servlets and jsps.
I notice in all of the documentation I find for mod_jk, an entire
directory (/examples/* being everyone's
André Malo wrote:
Where's the user base of mod_imap (installed by default) or mod_cern_meta or
the old outdated NCSA config directives? We add and add and add code -- which
is not actually bad. But where's the man with the broom?
The issue of unmaintained code is an important issue, but not one
On Wed, 21 Jul 2004 05:33:18 +0900 (JST), Tsuyoshi SASAMOTO
[EMAIL PROTECTED] wrote:
And... in perchild.c, I found setjmp/longjmp is used unsafely
(one jmpbuffer is shared by all threads).
patch looks reasonable on first glance; I'll look further with the
intention of committing soon-ish;
I sent an email to that address and it failed. Can somebody please tell me
what to do? Thank you all so much.
smime.p7s
Description: S/MIME cryptographic signature
On Tue, Jul 20, 2004 at 09:36:25PM -0400, Jeffrey K Pry wrote:
I sent an email to that address and it failed. Can somebody please tell me
what to do? Thank you all so much.
I just unsubbed the address manually. In the future, please save the
message you got when subscribing to a list to know how
70 matches
Mail list logo
