You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Unico Hommes <un...@hippo.nl> on 2004/03/17 16:57:55 UTC

cocoon.redirectTo broken

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

RE: cocoon.redirectTo broken

Posted by Carsten Ziegeler <cz...@s-und-n.de>.
The problem is due to the recent changes for internl redirect handling.
I reverted this change and it should work now again.

Carsten 

> -----Original Message-----
> From: Unico Hommes [mailto:unico@hippo.nl] 
> Sent: Wednesday, March 17, 2004 9:23 PM
> To: dev@cocoon.apache.org
> Subject: Re: cocoon.redirectTo broken
> 
> 
> I've added an test scenario and anteater testcase to show 
> this bug. See http://localhost:8888/test/sendpage/explain-test.html
> 
> --
> Unico
> 
> Unico Hommes wrote on 17-3-2004 17:14:
> 
> > 
> > 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
> 


Re: cocoon.redirectTo broken

Posted by Unico Hommes <un...@hippo.nl>.
I've added an test scenario and anteater testcase to show this bug. See 
http://localhost:8888/test/sendpage/explain-test.html

--
Unico

Unico Hommes wrote on 17-3-2004 17:14:

> 
> 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

Re: cocoon.redirectTo broken

Posted by Unico Hommes <un...@hippo.nl>.
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