We continue to have 1.3 servers because the Enhydra Director module,
needed for Enydra Application Server version 3, has not been ported to
Apache 2. The reason is that the Enhydra folks have long since
abandoned the protocol and now use AJP13, for which there is already
mod_jk2 and the AJP13
If you use rewritemaps in your httpd.conf base context and set virtual
hosts to inherit the rewrite options, it causes it to spawn addition
instances of the program for each virtual host.
Is there a reason it can't reuse the base contexts pipes to these
rewrite programs?
Byron
.
Byron
-Original Message-
From: Graham Leggett [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 22, 2004 8:32 AM
To: [EMAIL PROTECTED]
Subject: Re: Invitation to HTTPD commiters in tomcat-dev
Guernsey, Byron (GE Consumer Industrial) wrote:
We are using mod_proxy and a patched
I'm late joining this discussion, but wanted to add my 2 cents.
We are using mod_proxy and a patched mod_rewrite to do sticky load balancing.
Mod_rewrite supports cookies, but not session based cookies. I added this
functionality and posted the patch here (see mod_rewrite cookie patch
Just bringing this one up again and submitting it for anyone who would
like to test. Attached to this email is a new patch against 2.0.50 that
modifies mod_rewrite.c to support the setting of cookies which have no
domain specified (ie: set to 'null'), or no timeout specified ('null')
or no path
]
Sent: Thu 6/17/2004 10:21 AM
To: [EMAIL PROTECTED]
Cc:
Subject: PATCH - cookie expire (Was E: I'd like to make some contributions)
On Thu, 17 Jun 2004, Guernsey, Byron (GE Consumer Industrial) wrote:
Don't expect a quick
The CO/cookie flag
in mod_rewrite is potentially a very powerful tool, however as it stands now in
2.0.49, you cannot set session basedcookies (cookies which expire when the
browser is closed) and you cannot set cookies without specifying the
domain.
I had both of these
requirements
