Return-Path: Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 91843 invoked by uid 500); 4 Aug 2003 15:36:30 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 91826 invoked from network); 4 Aug 2003 15:36:29 -0000 Received: from node1a14f.a2000.nl (HELO naomi.webworks.nl) (24.132.161.79) by daedalus.apache.org with SMTP; 4 Aug 2003 15:36:29 -0000 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Subject: Setting response status code from flow Date: Mon, 4 Aug 2003 17:36:30 +0200 Message-ID: <84F0A43A4248CE45B5C0E20F4C40779C36CB26@naomi.webworks.nl> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Setting response status code from flow Thread-Index: AcNani19U7rkNzvfQC2hJwaScoZ4bQ== From: "Unico Hommes" To: X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi all, I would like to be able to response.setStatus from the flow. I have two scenarios I would like to use this: 1) In an authentication module where failure to authenticate should result in 401 in order to give the browser the chance to recover from being denied access to a certain resource. 2) In the davmap all responses that do not imply an http content body. Currently the only way to set the status code in cocoon is by specifying a status-code attribute on the serializer. This means that body-less responses can only be programmed using some dummy pipeline as is done in the current davmap sample. What do other think? Are these convincing use cases for adding response.setStatus to the FOM? Regards, Unico