Let's not make that document and say we did.

Specifically, let's incorporate that info into the Overrides: foo headers
in the directives tree, but write a simple script to just extract and build
a table of that gook for the docs.  We don't need one more doc to mess up
and allow to fall out of sync :(

Bill  

----- Original Message ----- 
From: "Cliff Woolley" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, September 03, 2001 10:39 PM
Subject: Re: FW: .htaccess doc is bogus (fwd)


> On Mon, 3 Sep 2001, Joshua Slive wrote:
> 
> > I forwarded it because it does point out a common problem people have.
> > Someone (perhaps their ISP) tells them to "do it with .htaccess".
> > They then come to the docs, and can't figure out what the heck
> > that means.  There are only a couple places in the docs that tell people
> > what an .htaccess file is and how to use it.
> >
> > I don't know what the solution is, but it is a problem I have heard more
> > than once.
> 
> Is there any document that summarizes "these are the directives that are
> valid from .htaccess" to keep you from having to look through the
> documentation of every single directive in every single module to figure
> it out?  Are there any samples of how to do the easy .htaccess tasks like
> setting up a plain and simple mod_auth or mod_access configuration?  I
> used to get asked these things ALL THE TIME by my users when I was a
> webmaster... I had to just have a stock .htaccess I could give them to
> learn from.  A document along those lines if it doesn't already exist
> would probably go a long way...
> 
> --Cliff
> 
> 
> --------------------------------------------------------------
>    Cliff Woolley
>    [EMAIL PROTECTED]
>    Charlottesville, VA
> 
> 
> 
> 
> ---------------------------------------------------------------------
> 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]

Reply via email to