Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 2148 invoked from network); 5 Nov 2003 15:25:33 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 5 Nov 2003 15:25:33 -0000 Received: (qmail 97910 invoked by uid 500); 5 Nov 2003 15:24:45 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 97842 invoked by uid 500); 5 Nov 2003 15:24:45 -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 97762 invoked from network); 5 Nov 2003 15:24:44 -0000 Received: from unknown (HELO kerberos) (62.116.51.59) by daedalus.apache.org with SMTP; 5 Nov 2003 15:24:44 -0000 Received: From mail.at.efp.cc ([62.116.51.60]) by kerberos (WebShield SMTP v4.5 MR1a); id 1068045884436; Wed, 5 Nov 2003 16:24:44 +0100 Received: from WRPO (wrpo.at.intra.efp.cc [194.107.80.153]) by mail.at.efp.cc (8.11.3/8.11.3/SuSE Linux 8.11.1-0.5) with ESMTP id hA5FOcX31652 for ; Wed, 5 Nov 2003 16:24:39 +0100 From: "Reinhard Poetz" To: Subject: RE: [Vote] empty HTTP responses [was Re: Cannot easily set http status] Date: Wed, 5 Nov 2003 16:23:59 +0100 Message-ID: <005501c3a3b0$d6c74120$8200000a@WRPO> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N From: Stefano Mazzocchi [mailto:stefano@apache.org] > Different story for Reinhard's concern, I think it's a valid point: > most situations on the web handle requests that return a payload... > having a way to signal that "hey, you are missing your payload" is a > good debugging advice and we wouldn't want to loose this for those > "rare" (in comparison) payload-less responses. > > So, what about > > cocoon.sendEmptyResponse(status-code) > +1 Reinhard