Alright, I finally isolated the problem: it's Mozilla Firebird 0.7! It has a bizarre problem where it sends 2 requests when I only click once. And somehow this only occurs when I use internal redirects within Cocoon. Go figure.


I verified that it works correctly in both KDE Konqueror on RedHat Linux 7.3 and IE6 on Windows XP.

Yeah, so I have no idea how to fix the Mozilla problem without an upgrade of the browser itself. Oh well. <sigh>

Thanks again for your help,

Sonny

From: "John L. Webber" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: map:redirect-to...
Date: Thu, 29 Jul 2004 09:18:43 +0200

Hi Sonny,

The only other thing I can suggest trying is to reproduce the bug with an alternate matcher, using different redirect resources and a different action. If the bug doesn't happen then, try swapping in your actual resources one at a time, and then your action. Something like:

<map:match pattern="secure/reallySimpleTest">
  <map:act type="always-succeeds">
    <map:redirect-to uri="cocoon:/pageExists1"/>
  </map:act>
  <map:redirect-to uri="cocoon:/pageExists2"/>
</map:match>

If that works as expected (i.e. no bug), try replacing the first redirect with your actual redirect. Of course, you'll have to create the new resources first!

Good luck,

John


Sonny Sukumar wrote:

Hey John,

I took your advice and spent some time culling through sitemap.log and discovered that BOTH redirects are taking place when I use internal redirects...it's just that the "test failed" redirect happens second, so I always see that result page (even though the action's operations in modifying the database, etc. are performed successfully).

Why this happens is still a mystery to me, but here's the sitemap log info showing this:

INFO (2004-07-28) 10:47.42:387 [sitemap] (/secure/doTest) http8443-Processor2/RedirectToURINode: Redirecting to 'cocoon:/showTestSucceededPage' at file:/usr/local/tomcat/webapps/cocoon/sitemap.xmap:1750:62

INFO (2004-07-28) 10:47.42:388 [sitemap] (/secure/doTest) http8443-Processor2/ForwardRedirector: Redirecting to 'cocoon:/showTestSucceededPage'

INFO (2004-07-28) 10:47.42:711 [sitemap] (/secure/doTest) http8443-Processor2/RedirectToURINode: Redirecting to 'cocoon:/showTestFailedPage' at file:/usr/local/tomcat/webapps/cocoon/sitemap.xmap:1755:68

INFO (2004-07-28) 10:47.42:712 [sitemap] (/secure/doTest) http8443-Processor2/ForwardRedirector: Redirecting to 'cocoon:/showTestFailedPage'

So I then tried--just for the heck of it--putting an html serializer right after the first redirect like this:

<map:match pattern="secure/doTest">
 <map:act type="perform-test">
   <!-- Test succeeded. -->
   <map:redirect-to uri="cocoon:/showTestSucceededPage"/>
   <map:serialize type="html"/>
 </map:act>

 <!-- Test failed. -->
 <map:redirect-to uri="cocoon:/showTestFailedPage"/>
</map:match>

And of course that didn't work either. :-) Sooo...maybe there's a bug with internal redirects?

BTW, I'm using the absolute latest stable version of Cocoon (2.1.5.1) on Tomcat 4.1.30. I upgraded just a few days ago...

Sonny

--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]


_________________________________________________________________
Don’t just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/



--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to