Re: Going to other context and/or server in 1.1

[Eddie Bush]

+1 - that would simplify things a great deal.

My idea was to have a static protocol list we'd iterate over - but I like yours much better.

Craig R. McClanahan wrote:

On Fri, 18 Oct 2002, David Graham wrote:

Date: Fri, 18 Oct 2002 09:29:04 -0600
From: David Graham <[EMAIL PROTECTED]>
Reply-To: Struts Developers List <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Going to other context and/or server in 1.1

I thought of the http:// matching as well.  Are there any cases when this
logic wouldn't work?  Hardcoding the protocol may be a bad idea.

Failure case:  https://www.mysecuresite.com

Maybe we need an "absolute" attribute on ForwardConfig (and therefore
ActinForward)?

--
Eddie Bush




--
To unsubscribe, e-mail:   <mailto:struts-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org>