On Thu, 8 Nov 2012 11:18:37 +0100 (CET) Stefan Fritsch <s...@sfritsch.de> wrote:
> On Wed, 7 Nov 2012, Tim Bannister wrote: > > > On 7 Nov 2012, at 11:26, Stefan Fritsch wrote: > >> If a method is not registered, bail out early. > > > > > > Good idea, but it would be nice to be able to use <Limit> or <LimitExcept> > > to re-allow it. I'd disagree with that mechanism. But as to your point: > I intended to add a directive to easily register custom methods (i.e. call > ap_method_register()). Do you think there is reason to allow arbitrary > methods, and not just a configured list of allowed ones? If methods are to be actively checked, a module needs an API to register a method with the checker. A configuration option might still be required for backends (e.g. proxy or CGI) but would perhaps be secondary? -- Nick Kew
