Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 62173 invoked by uid 500); 11 Nov 2000 05:35:40 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 62162 invoked from network); 11 Nov 2000 05:35:39 -0000 Date: Fri, 10 Nov 2000 13:38:22 -0800 From: "Roy T. Fielding" To: new-httpd@apache.org Subject: Re: [PATCH] check Expect after post_read_request Message-ID: <20001110133822.A7410@mana.ebuilt.com> References: <200011102120.NAA07360@mana.ebuilt.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.9i In-Reply-To: ; from rbb@covalent.net on Fri, Nov 10, 2000 at 09:26:20PM -0800 X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N > Is this done better by input filters in 2.0? I'm just asking here, Maybe. The tricky part is when the check is done. It has to be after any extensions (input filters or regular modules) have had a chance to check Expect and remove anything that they will handle, but before any method is applied to a resource. I haven't looked at where I would place it in the current 2.0 tree. ....Roy