where is the problem?
Instead of <xsp-response:send-redirect url="any"/> you create a own element like <redirect url="any"/> in the XML. This is processed by a transformer to <meta http-equiv="Refresh" content="0; URL=any"/> and sent to the browser. Even if it's a very poor solution, there shell be no problem with it. I prefer the test while setting up the pipeline.
Regards,
Joerg
Artur Bialecki wrote:
-----Original Message-----
From: Ilya A. Kriveshko [mailto:ilya@;kaon.com] Sent: November 8, 2002 10:41 AM
To: [EMAIL PROTECTED]
Subject: Re: Redirect in XSP
If you want to redirect the browser to a new URL after the
pipeline has been constructed and the generation has (possibly)
started, you can do that by outputting the <META> tag in the
output HTML.
<meta http-equiv="Refresh" content="0; URL=/some/local/url"/>
or
<meta http-equiv="Refresh" content="0; URL=http://some.com/other/url"/>
"0" means no delay.
How would this work if half of my page has already been sent to the browser including the </HEAD> tag? Please clarify.Artur...
--------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
