Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Mime-Version: 1.0 (Apple Message framework v609)
Content-Transfer-Encoding: 7bit
Message-Id: <26AA165A-3E17-11D8-A301-000393D2CB02@apache.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed
To: Cocoon <dev@cocoon.apache.org>
From: Stefano Mazzocchi <stefano@apache.org>
Subject: [Bug?] absolute redirection in flow appears not to be proxy safe
Date: Sat, 3 Jan 2004 19:03:36 +0100

I came across a very weird problem today. I had two cocoon applications 
that were once running in different JVM instances, both mapped to / and 
I moved them into a single Jetty instance mapped on /A and /B (for 
simplicity).

Then I modified the ProxyPass settings and used the jetty web.xml trick 
to change the cookie path.

Now, the interesting thing was that while /A performed just like 
before, /B had a wierd problem: "redirects" were absolute to the 
"webapp server", not to the "web server".

Both apps had the same exact version of cocoon (compiled this morning).

After careful examination and extensive protocol dump, I was able to 
understand that while /A used

  cocoon.redirectTo(../../index);

/B used

  cocoon.redirectTo(/index);

and both turn up to the in the same position, but while the first 
actually works (the redirect is "remapped" to the original Proxy URL, 
not to the appserver one which is obviously firewalled), the second 
doesn't do remapping and the web application fails because it tries to 
connect to the webapp directly

[actually it's even worse, because it tries to connect to the ProxyPass 
setting, which are http://localhost:8000/ in my case, so it tries to 
connect to *your* machine!]

The interesting thing is that this worked perfectly in the past, when 
both were mapped to /, but I can't tell what broke since I moved them 
*and* change the version of cocoon at the same time.

Did anybody experience a similar behavior?

--
Stefano.