Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Message-ID: <40FE4C03.5080202@sharp.fm>
Date: Wed, 21 Jul 2004 12:57:07 +0200
From: Graham Leggett <minfrin@sharp.fm>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.6) Gecko/20040113
MIME-Version: 1.0
To: Tomcat Developers List <tomcat-dev@jakarta.apache.org>
CC: dev@httpd.apache.org
Subject: Re: Invitation to HTTPD commiters in tomcat-dev
References: <20040721080018.905F349DC9@dns1.vodatel.hr>
 <40FE44D3.5060500@sharp.fm> <40FE46ED.3010507@apache.org>
In-Reply-To: <40FE46ED.3010507@apache.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Henri Gomez wrote:

> BTW, could we expect to be able to use in proxy_ajp URL like
> ajp://VIRTUALNAME, where VIRTUALNAME could be the name of an
> AJP cluster backend ?

That would be up to proxy_ajp to decide, so yes.

What happens is that when the config says

ProxyPass /myApp ajp://VIRTUALNAME

and the user requests the URL /myApp/index.jsp, proxy will give 
proxy_ajp an URL that looks like this:

ajp://VIRTUALNAME/index.jsp

It's up to proxy_ajp to understand what that means.

> Also could we expect the handling of failure via mod_proxy + proxy_xxx , 
> ie: when a tomcat respond 503 or 400, to be able to switch to another
> tomcat in the cluster. It's a mandatory feature for now.

Proxy already loops around and tries again on connection failure to a 
different server in the backend. If proxy cannot handle a 503 or a 400, 
then it can be made to handle it - again it's a feature that would be 
really useful regardless of the protocol.

Regards,
Graham
--