Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <4058796C.1070508@hippo.nl>
Date: Wed, 17 Mar 2004 17:14:36 +0100
From: Unico Hommes <unico@hippo.nl>
Organization: Hippo
User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: cocoon.redirectTo broken
References: <40587583.1000507@hippo.nl>
In-Reply-To: <40587583.1000507@hippo.nl>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


Oops, it's something else. It is related to cocoon.sendPage(). It 
doesn't consider internal-only pipelines:

sitemap.xmap:
<map:pipeline internal-only="true">
   <map:match pattern="internal">
    ...
   </map:match>
</map:pipeline>

<map:pipeline>
   <map:match pattern="**">
     <map:call function="sendInternal"/>
   </map:match>
</map:pipeline>

flow.js:
function sendInternal() {
   cocoon.sendPage("internal",null);
}

Requesting anything will cause an infinite loop.

Setting internal-only="false" on the first pipeline fixes it again.

--
Unico

Unico Hommes wrote on 17-3-2004 16:57:

> 
> It seems that cocoon.redirectTo FOM function is now doing an internal 
> redirect instead of causing a browser redirect. Calling 
> cocoon.redirectTo("somewhere") shows the following message in the 
> sitemap log: INFO    (2004-03-17) 16:44.43:471   [sitemap] 
> (/samples/slide/content/) PoolThread-4/ForwardRedirector: Redirecting to 
> 'cocoon:/somewhere/'.
> 
> My first guess was that the following patch was the reason: 
> http://issues.apache.org/bugzilla/show_bug.cgi?id=26854 . But the 
> problem seems to persist when I undo that change. Anybody know what has 
> caused this or how to fix it?
> 
> -- 
> Unico