On Wed, 21 Aug 2002, Thomas [iso-8859-1] Sjögren wrote: > On Wednesday 21 August 2002 10:48, Michael wrote: > > > Fine. But I think it wouldn't hurt to at least mention the > > scenario in the "security document" starting section and > > link to the tutorial named above - as there may be readers > > who start searching for their solution here. > > Since many of the topics in the scenarios already has been covered, > either in the security doc or elsewhere wouldn't the simplest > solution be to do something like this: > > Scenario 1: Server wants to control which clients access some > protected files. > Topics: Authentication (<auth.html>, <mod_auth>, <mod_auth_dbm>, > <mod_auth_anon>), Directory Browsing, > ScriptAlias, .htaccess <.htaccess.html>, ErrorDocument,... > > Where <*> means a link to document.
Yes, I think something like that is appropriate. -- And everyone said, "If we only live, We too will go to sea in a Sieve - To the hills of the Chankly Bore!" (The Jumblies, by Edward Lear) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
