Return-Path: <new-httpd-owner-new-httpd-archive=hyperreal.org@apache.org>
Delivered-To: new-httpd-archive@hyperreal.org
Received: (qmail 27190 invoked by uid 6000); 7 Jan 1999 19:13:30 -0000
Received: (qmail 27093 invoked from network); 7 Jan 1999 19:13:18 -0000
Received: from mail1.microsoft.com (131.107.3.125)
  by taz.hyperreal.org with SMTP; 7 Jan 1999 19:13:18 -0000
Received: by mail1.microsoft.com with Internet Mail Service (5.5.2524.0)
	id <CPZ40ZK8>; Thu, 7 Jan 1999 11:12:49 -0800
Message-ID: <8B57882C41A0D1118F7100805F9F68B50631A7DE@RED-MSG-45>
From: Josh Cohen <joshco@microsoft.com>
To: "'new-httpd@apache.org'" <new-httpd@apache.org>
Subject: RE: Suggested patch for unkown methods in <Limit> 
Date: Thu, 7 Jan 1999 11:10:12 -0800 
X-Mailer: Internet Mail Service (5.5.2524.0)
Sender: new-httpd-owner@apache.org
Precedence: bulk
Reply-To: new-httpd@apache.org

Excellent.  I noticed the #ifdef APACHE_RELEASE
stuff in mod_dav that is aware of the 1.3.4
new methods.

Id still like to see the UNKNOWN patch I suggested
in 1.3.4 so that unknown methods cam be limited.
Things like DASL 'SEARCH' and GENA come to mind.

Who is the best person to plead with to get this
patch in 1.3.4?

thanks
josh

> -----Original Message-----
> From: Greg Stein [mailto:gstein@lyra.org]
> Sent: Wednesday, January 06, 1999 11:45 PM
> To: Josh Cohen
> Cc: new-httpd@apache.org
> Subject: RE: Suggested patch for unkown methods in <Limit> 
> 
> 
> I agree that it would be a DAV blocker... However, the DAV methods are
> available to the Limit directive in 1.3.4 (coming RSN). I've 
> been waiting
> for them, too :-)
> 
> Cheers,
> -g
> 
> > -----Original Message-----
> > From: new-httpd-owner@apache.org 
> [mailto:new-httpd-owner@apache.org]On
> > Behalf Of Josh Cohen
> 
> > Sent: Wednesday, January 06, 1999 7:38 PM
> > To: 'new-httpd@apache.org'
> > Subject: RE: Suggested patch for unkown methods in <Limit>
> >
> >
> > I totally agree with your assessment that a stronger, long
> > term solution is needed.
> > However, I would guess this is an adoption blocker for DAV.
> > You cant do the common task of setting a directory read/write
> > via DAV for the author and read only (via GET) for everyone else.
> >
> > I'd ask that if you do a minor rev, then this should be included.
> > Its simple and reduces the pain of trying to deploy apache as
> > a DAV platform.
> >
> > > -----Original Message-----
> > > From: Roy T. Fielding [mailto:fielding@kiwi.ics.uci.edu]
> > > Sent: Wednesday, January 06, 1999 5:51 PM
> > > To: new-httpd@apache.org
> > > Subject: Re: Suggested patch for unkown methods in <Limit>
> > >
> > >
> > > >I quite like the idea of UNKNOWN, but I'm not so sure I'm
> > > keen that PROPPATCH
> > > >and PROPFIND are treated as such. Looks to me like we need
> > > to make a more
> > > >serious change (i.e. modules register known methods and we
> > > allow Limit to apply
> > > >to those and UNKNOWN to anything else).
> > >
> > > That's on the list of 2.0 things.  I was thinking of adding a
> > > LimitExcept
> > > (a logical "everything except the following methods"),
> > since otherwise
> > > the config file has to be kept in sync with the list of
> > known methods.
> > > Not enough time to do it though.
> > >
> > > ....Roy
> > >
> >
>