> note that this situation is a bit different from the others since the
> apache core will pass ALL requirements (limited or not) to every auth
> module. Each individual auth module can make its own decision in this
> case (i.e. there are requirements for some methods and no requirements
> for o
> DON'T second-guess them. Since no restrictions have been put in place,
> don't try to apply any. There may be Auth*File and Require directives
> in .htaccess files within the above scope -- you don't know.
Good point - I'll change that in the version I have now.
Dw.
On Mon, 22 Jul 2002, Rodent of Unusual Size wrote:
> [EMAIL PROTECTED] wrote:
> >
...snip
> >
> >
> > AuthTypebasic
> > AuthNameRestricted area
> >
> > require valid-user
> >
> >
> >
> > Same here when using a GET
[EMAIL PROTECTED] wrote:
>
> Opinions - not on what happens to day in 1.3 but what should happen in a
> perfect world:
>
> Given a config like this:
>
>
> AuthTypebasic
> AuthNameRestricted area
>
>
> What should happen ? Allowed in with, or wi
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] wrote:
> Opinions - not on what happens to day in 1.3 but what should
> happen in a
> perfect world:
>
> Given a config like this:
>
>
> AuthTypebasic
> AuthNameRestricted area
>
>
> What should happen ? Al
