cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kjetil Kjernsmo <Kjetil.Kjern...@computas.com>
Subject Re: Redirecting with 303
Date Mon, 11 Aug 2008 07:42:49 GMT
On Friday 08 August 2008 16:23:43 Jasha Joachimsthal wrote:
> After a map:redirect-to the pipeline ends its execution. The
> map:serialized will not be called. Setting status-code="303" on the
> map:redirect-to is not (yet) supported.

OK!

> Doesn't a 302 do what you want to achieve?

Nope. The semantics of 302 is very different, with 302, both URIs deal with 
the same resource, it is just that they are temporarily the same. What we are 
doing here is dealing with URIs for things that are not network-retrievable, 
such as people. In this context, a 303 means "you cannot retrieve a person 
through the network, but here is a description of the person". This is a key 
concept in the Semantic Web.

So, what would the simplest way to do this with Cocoon be?

Kind regards 

Kjetil Kjernsmo
-- 
Senior Knowledge Engineer
Direct: +47 6783 1136 | Mobile: +47 986 48 234
Email: kjetil.kjernsmo@computas.com   
Web: http://www.computas.com/

|  SHARE YOUR KNOWLEDGE  |

Computas AS  Vollsveien 9, PO Box 482, N-1327 Lysaker | Phone:+47 6783 1000 | 
Fax:+47 6783 1001


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Mime
View raw message