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
...
--
Wayne S. Frazee
Any sufficiently developed bug is indistinguishable from a feature.
On Tue, 2004-07-20 at 08:51, Henri Gomez wrote:
Manni Wood wrote:
- Could mod_proxy be open to support AJP/1.x as tomcat connections ?
- Should we learn from mod_proxy to redesign something using AJP
: Tuesday, July 20, 2004 11:36 AM
To: [EMAIL PROTECTED]
Subject: Re: Invitation to HTTPD commiters in tomcat-dev
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
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
, 2004 11:51 AM
To: [EMAIL PROTECTED]
Cc: Tomcat Developers List
Subject: Re: Invitation to HTTPD commiters in tomcat-dev
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
be? I'd love to help.
-Manni
-Original Message-
From: Henri Gomez [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 20, 2004 11:53 AM
To: [EMAIL PROTECTED]
Subject: Re: Invitation to HTTPD commiters in tomcat-dev
Manni Wood wrote:
Anyway, for business sites, any servlet being able to know
To: [EMAIL PROTECTED]
Cc: Tomcat Developers List
Subject: Re: Invitation to HTTPD commiters in tomcat-dev
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
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
, but, Andre, as you point out, there
are good reasons for your line of thinking.
-Manni
-Original Message-
From: André Malo [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 20, 2004 1:59 PM
To: [EMAIL PROTECTED]
Subject: Re: Invitation to HTTPD commiters in tomcat-dev
* Manni Wood [EMAIL
: Invitation to HTTPD commiters in tomcat-dev
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
Ummm... as the person who created the new bug (by successfully stomping
a years-old one in the same module), I have a particular interest in the
solution of this bug. I had submitted a patch to the 2.x series on
bugzilla, and, eventually, things died down with no direction, so I
waited for
did was take the latest/working 2.0.x patch (from the PR
report), and backported it to 1.3. I didn't patch the 2.x
trees at the same time, because I simply forgot. :/
I believe Cliff is doing that as we speak.
On Feb 18, 2004, at 2:33 PM, Manni Wood wrote:
Ummm... as the person who created
Yeah, I have to take responsibility for this bug. Apologies to all. Fans
of irony will appreciate that I unwittingly introduced this new bug
while solving a long-standing cookie header parsing bug! Ouch...
Thanks, Cliff, for posting the note on httpd.apache.org.
-Manni
-Original
it wrong?
On Wednesday, October 15, 2003, at 04:52 PM, Cliff Woolley wrote:
Attached is a patch by Manni Wood for the 1.3.x series that fixes a
problem in mod_usertrack where the usertracking cookie will be
incorrectly identified. It simply switches from a strstr to a regex
match
If you look at recent archives of this mailing list, my submission for a
patch to mod_usertrack will show you a robust way of searching for
cookies in the cookie header.
In the current codebase, mod_usertrack shows you a way of doing this as
well, but is is not bullet-proof: read my analysis of
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 25, 2003 6:00 PM
To: [EMAIL PROTECTED]
Subject: RE: mod_usertrack bugfix patch
On Tue, 25 Feb 2003, Manni Wood wrote:
Kind of funny. While reading all these helpful e-mails, I was telling
myself so really, what I need to do is build some sort
, if you'd like (and
encourage you to do the same, naturally). Is there a standard way the Apache Group
runs tests on new code to see if it meets performance guidelines? I'm sure the
performance hit won't be any worse than for mod_alias.
-Manni
Manni Wood
processing the cookie header as soon as I find the tracking cookie, and don't
bother putting the cookies into an ap_table at all.
Does this sound like the best approach to you? It wouldn't take me very long to code.
-Manni
Manni Wood, Programmer, Digitas
800
Manni Wood, Programmer, Digitas
800 Boylston Street, Boston, MA, 02199
617 867 1881 [EMAIL PROTECTED]
Most men would rather die than think. Many do.--Bertrand Russell
-Original Message-
From: Sander Holthaus - Orange XL [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 25, 2003 5
for an improved algorithm) to deliver improved accuracy *and* performance
finding the cookie in mod_usertrack.
I guess it's time to get hacking.
-Manni
Manni Wood, Programmer, Digitas
800 Boylston Street, Boston, MA, 02199
617 867 1881 [EMAIL PROTECTED
21 matches
Mail list logo
