forget that patch - it probably won't do what you want either...
I was mainly thinking about limiting the scope of DispatchPrefix for
security reasons (keeping people from being sloppy)...
if you don't think this is too much of a concern, then perhaps I'll change
everything to OR_ALL?
--Geoff
> -----Original Message-----
> From: Geoffrey Young [mailto:[EMAIL PROTECTED]]
> Sent: Friday, December 01, 2000 2:24 PM
> To: 'Matt Sergeant'; [EMAIL PROTECTED]
> Subject: RE: Apache::Dispatch directives
>
>
> all options are RSRC_CONF | ACCESS_CONF except
> DispatchPrefix, which is
> ACCESS_CONF...
>
> my thought on making DispatchPrefix local only to directories was that
> Apache::Dispatch was specific to a <Location> tag: other
> options I thought
> could be applied globally, but you wouldn't want My::Handler
> to resolve from
> /foo and /bar... but maybe you would? I dunno...
>
> anyway, I don't ordinarily use .htaccess, so I didn't test
> Apache::Dispatch
> with them in mind...
>
> what effect does .htaccess have on DIR_MERGE?
>
> anyway, you can try this and see if it has hany ill effects -
> I can't think
> of any. DispatchFilter will have to stay the way it is,
> though, because I
> didn't feel like writing a huge if/else block to capture all the
> possibilities of mixing PerlSetVar Filter On with DispatchFilter :)
>
> Index: Makefile.PL
> ===================================================================
> RCS file: /usr/local/CVS/Apache-Dispatch/Makefile.PL,v
> retrieving revision 1.12
> diff -u -r1.12 Makefile.PL
> --- Makefile.PL 2000/11/06 16:30:07 1.12
> +++ Makefile.PL 2000/12/01 19:22:08
> @@ -14,7 +14,7 @@
> { name => 'DispatchPrefix',
> errmsg => 'a class to be used as the base class',
> args_how => 'TAKE1',
> - req_override => 'ACCESS_CONF', },
> + req_override => 'OR_AUTHCFG', },
>
> #------------------------------------------------------------------
> # DispatchExtras defines the extra dispatch methods to enable
> @@ -22,7 +22,7 @@
> { name => 'DispatchExtras',
> errmsg => 'choose any of: Pre, Post, or Error',
> args_how => 'ITERATE',
> - req_override => 'RSRC_CONF | ACCESS_CONF', },
> + req_override => 'OR_ALL', },
>
> #------------------------------------------------------------------
> # DispatchStat enables module testing and subsequent reloading
> @@ -30,7 +30,7 @@
> { name => 'DispatchStat',
> errmsg => 'choose one of On, Off, or ISA',
> args_how => 'TAKE1',
> - req_override => 'RSRC_CONF | ACCESS_CONF', },
> + req_override => 'OR_ALL', },
>
> #------------------------------------------------------------------
> # DispatchAUTOLOAD defines AutoLoader behavior
> @@ -38,7 +38,7 @@
> { name => 'DispatchAUTOLOAD',
> errmsg => 'choose one of On or Off',
> args_how => 'TAKE1',
> - req_override => 'RSRC_CONF | ACCESS_CONF', },
> + req_override => 'OR_ALL', },
>
> #------------------------------------------------------------------
> # DispatchISA is a list of modules your module should inherit from
> @@ -46,7 +46,7 @@
> { name => 'DispatchISA',
> errmsg => 'a list of parent modules',
> args_how => 'ITERATE',
> - req_override => 'RSRC_CONF | ACCESS_CONF', },
> + req_override => 'OR_ALL', },
>
> #------------------------------------------------------------------
> # DispatchFilter makes the dispatched handler Apache::Filter aware
>
> > -----Original Message-----
> > From: Matt Sergeant [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, December 01, 2000 1:55 PM
> > To: [EMAIL PROTECTED]
> > Subject: Apache::Dispatch directives
> >
> >
> > .... do not seem to be allowed in .htaccess files. I don't
> > see a reason for
> > this restriction, Geoff ???
> >
> > Particularly, I want to just be able to say:
> >
> > DispatchPrefix MyModule
> >
> > in a .htaccess file and have it just work.
> >
> > --
> > <Matt/>
> >
> > /|| ** Director and CTO **
> > //|| ** AxKit.com Ltd ** ** XML Application Serving **
> > // || ** http://axkit.org ** ** XSLT, XPathScript, XSP **
> > // \\| // ** Personal Web Site: http://sergeant.org/ **
> > \\//
> > //\\
> > // \\
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
