httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Stein" <gst...@lyra.org>
Subject RE: Suggested patch for unkown methods in <Limit>
Date Thu, 07 Jan 1999 07:45:19 GMT
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
> >
>


Mime
View raw message