I did try upgrading but I couldn't install Firefox 0.9 because of some
library dependency that I couldn't resolve. I figure I'd like to upgrade my
OS soon though, so I figured I'd wait until then to try again.
From: John L. Webber [EMAIL PROTECTED]
Have you tried Firefox 0.9? (It's no longer
PROTECTED]
Subject: Mozilla request parameters (was: Re: map:redirect-to...)
Date: Wed, 04 Aug 2004 09:03:38 +0200
Sonny,
We've had problems with image buttons and request parameters; for example
if the button has the name saveme, Mozilla sends request parameters
saveme, saveme.x and saveme.y, while
Have you tried Firefox 0.9? (It's no longer called Firebird)
John
Sonny Sukumar wrote:
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
Sonny,
We've had problems with image buttons and request parameters; for
example if the button has the name saveme, Mozilla sends request
parameters saveme, saveme.x and saveme.y, while Konqueror and IE
only send saveme.x and saveme.y. Since we use almost exclusively
Mozilla internally, this
: 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
the
steps I followed:
1.) I first introduced new internal redirects, commenting out the old
ones:
map:match pattern=secure/doTest
map:act type=perform-test
!-- Test succeeded. --
!--map:redirect-to uri=cocoon:/showTestSucceededPage/--
map:redirect-to uri=cocoon:/myTestSucceeded/
/map:act
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
-test
!-- Test succeeded. --
!--map:redirect-to uri=cocoon:/showTestSucceededPage/--
map:redirect-to uri=cocoon:/myTestSucceeded/
/map:act
!-- Test failed. --
!--map:redirect-to uri=cocoon:/showTestFailedPage/--
map:redirect-to uri=cocoon:/myTestFailed/
/map:match
This actually works
failing or did you mean some type of Exception being
thrown from it?
map:match pattern=secure/doTest
map:act type=perform-test
!-- Test succeeded. --
map:redirect-to uri=cocoon:/showTestSucceededPage/
/map:act
!-- Test failed. --
map:redirect-to uri=cocoon:/showTestFailedPage/
/map:match
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
use
HTTP redirects.
I just don't wanna use HTTP redirects for this. :-/
I'm having a strange problem with map:redirect-to, where it doesn't seem
to work right when I use the cocoon:/ protocol. Here's my example code:
map:match pattern=secure/doTest
map:act type=perform-test
!-- Test
problem with map:redirect-to, where it doesn't seem
to work right when I use the cocoon:/ protocol. Here's my example code:
map:match pattern=secure/doTest
map:act type=perform-test
!-- Test succeeded. --
map:redirect-to uri=cocoon:/showTestSucceededPage/
/map:act
!-- Test failed
with map:redirect-to, where it doesn't seem
to work right when I use the cocoon:/ protocol. Here's my example code:
map:match pattern=secure/doTest
map:act type=perform-test
!-- Test succeeded. --
map:redirect-to uri=cocoon:/showTestSucceededPage/
/map:act
!-- Test failed. --
map:redirect-to uri
Hey guys,
I'm having a strange problem with map:redirect-to, where it doesn't seem to
work right when I use the cocoon:/ protocol. Here's my example code:
map:match pattern=secure/doTest
map:act type=perform-test
!-- Test succeeded. --
map:redirect-to uri=cocoon:/showTestSucceededPage
Title: Problems using map:redirect-to uri=
Hello,
I'm trying to use the redirect tag inside a sitemap but I experience some problems.
I'm using cocoon 2.1.3. , Tomcat 4.0
Part of my sitemap looks as:
The first pipeline calls an action which stores the next-page-to-go in the variable
Ralph Goers wrote:
I tried putting a map:redirect-to in my error handling section and got an
error processing the sitemap saying that it isn't allowed? Anybody know
why?
There were hard discussions about it:
http://marc.theaimsgroup.com/?t=10515986721r=1w=2
http://marc.theaimsgroup.com/?t
it in the Map,
but this feels akward.
Ralph
-Original Message-
From: Joerg Heinicke [mailto:[EMAIL PROTECTED]
Sent: Friday, November 21, 2003 6:01 AM
To: [EMAIL PROTECTED]
Subject: Re: map:redirect-to and error handling
Ralph Goers wrote:
I tried putting a map:redirect-to in my
I tried putting a map:redirect-to in my error handling section and got an
error processing the sitemap saying that it isn't allowed? Anybody know
why? However, the documentation on error handling shows an example using a
(presumably) fictional action as map:act type=redirect and warning to do
]
- Original Message -
From: Sonny Sukumar [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, August 17, 2003 9:11 PM
Subject: new Request for internal map:redirect-to's?
Does anybody know if a new Request instance is created when one does an
internal redirect. Like this:
map:match pattern
on 2.1 can comment?
Geoff, anyone else?
Sonny
From: Jay Freeman \(saurik\) [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: new Request for internal map:redirect-to's?
Date: Mon, 18 Aug 2003 01:49:40 -0500
Sonny:
I was under the impression that not only does a new
Sonny:
Oh, I'm sorry, I didn't even pay attention to that. :(
Sincerely,
Jay Freeman (saurik)
[EMAIL PROTECTED]
- Original Message -
From: Sonny Sukumar [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, August 18, 2003 2:19 AM
Subject: Re: new Request for internal map:redirect-to's
Sonny:
Isn't what you're asking for capable of being done with a map:read
src=cocoon:/../ instead of a map:redirect-to/? Or is your actually
usage case more complicated than your examples. I could almost understand
redirect-to trying to simulate what would happen if a Location header _had_
been
22 matches
Mail list logo
