[docs] Change in AdvControllingAccessToCertain made by Stewart Barnett
Mike Heins
docs@icdevgroup.org
Thu Jan 23 13:57:00 2003
Quoting Wiki Watch (docs@icdevgroup.org):
> You can visit the live page at this URL:
> http://www.icdevgroup.org/i/doc/wiki/AdvControllingAccessToCertain.html
>
> --- tmp/ZMLLBY5N:216.54.52.220.previous Thu Jan 23 13:44:37 2003
> +++ tmp/ZMLLBY5N:216.54.52.220.current Thu Jan 23 13:44:37 2003
> @@ -1,53 +1,46 @@
> -=head2 Controlling Access to Certain Pages
> -
> -If the directory containing the page has a file .access and that
> -file's size is zero bytes, access can be gated in one of several ways.
> -
> -=over 4
> -
> -=item 1.
> -
> -If the file .access_gate is present, it will be read and scanned
> -for page-based access. The file has the form:
> +<HTML>
>
> +<!-- This file was generated using SDF 2.001 by
> + Ian Clatworthy (ianc@mincom.com). SDF is freely
> + available from http://www.mincom.com/mtr/sdf. -->
> +
Hmm. This is a bit problematic -- it would be very difficult to merge
this into the docs....
> +<HEAD>
> +<TITLE>Advanced Interchange Topics: Controlling Access to Certain Pages</TITLE>
> +<LINK REL="stylesheet" TYPE="text/css" HREF="docs.css">
> +<LINK REL="stylesheet" TYPE="text/css" HREF="docs.css">
> +</HEAD>
> +<BODY BGCOLOR="ffffff" LINK="993333">
> +
> +<DIV CLASS="header">
> +<DIV CLASS="navigate">
> +<P ALIGN="Center"><A HREF="icadvanced_11.html">Parent Topic</A> | <A HREF="icadvanced_11.html">Previous Topic</A> | <A HREF="icadvanced_13.html">Next Topic</A> <BR><A HREF="../index.html" TARGET="_top">Documentation Index</A></P>
> +</DIV>
> +</DIV>
> +<DIV CLASS="main">
> +<H2>4.1. Controlling Access to Certain Pages</H2>
> +<P>If the directory containing the page has a file <TT>.access</TT> and that file's size is zero bytes, access can be gated in one of several ways.</P>
> +<OL>
> +<LI>If the file <TT>.access_gate</TT> is present, it will be read and scanned for page-based access. The file has the form:</OL>
> +<PRE>
> page: condition
> -
> -=back
> *: condition
> -
> -=over 4
> -
> -=item
> -
> -The page is the file name of the file to be controlled (the .html
> -extension is optional). The condition is either a literal Yes/No
> -or Interchange tags which would produce a Yes or No (1/0 work
> -just fine, as do true/false).
> -
> -The entry for * sets the default action if the page name is not
> -found. If pages will be allowed by default, set it to 1 or Yes.
> -If pages are to be denied by default in this directory, leave blank or
> -set to No. Here is an example, for the directory controlled,
> -having the following files:
> -
> +</PRE>
> +<UL>
> +The <TT>page</TT> is the file name of the file to be controlled (the .html extension is optional). The <TT>condition</TT> is either a literal <TT>Yes/No</TT> or Interchange tags which would produce a <TT>Yes</TT> or <TT>No</TT> (1/0 work just fine, as do true/false).
> +<BR>
> +The entry for <TT>*</TT> sets the default action if the page name is not found. If pages will be allowed by default, set it to <TT>1</TT> or <TT>Yes</TT>. If pages are to be denied by default in this directory, leave blank or set to <TT>No</TT>. Here is an example, for the directory <TT>controlled</TT>, having the following files:</UL>
> +<PRE>
> -rw-rw-r-- 1 mike mike 0 Jan 8 14:19 .access
> -
> -=back
> -rw-rw-r-- 1 mike mike 185 Jan 8 16:00 .access_gate
> -rw-rw-r-- 1 mike mike 121 Jan 8 14:59 any.html
> -rw-rw-r-- 1 mike mike 104 Jan 8 14:19 bar.html
> -rw-rw-r-- 1 mike mike 104 Jan 8 14:19 baz.html
> -rw-rw-r-- 1 mike mike 104 Jan 8 14:19 foo.html
> -
> -=over 4
> -
> -=item
> -
> -The contents of .access_gate:
> -
> +</PRE>
> +<UL>
> +The contents of <TT>.access_gate</TT>:</UL>
> +<PRE>
> foo.html: [if session username eq 'flycat']
> -
> -=back
> Yes
> [/if]
> bar: [if session username eq 'flycat']
> @@ -56,41 +49,23 @@
> [/if]
> baz: yes
> *: [data session logged_in]
> +</PRE>
> +<UL>
> +The page <TT>controlled/foo</TT> is only allowed for the logged-in user <B>flycat</B>.
> +<BR>
> +The page <TT>controlled/bar</TT> is allowed for the logged-in user <B>flycat</B>, or if the scratch variable <TT>allow_bar</TT> is set to a non-blank, non-zero value.
> +<BR>
> +The page <TT>controlled/baz</TT> is always allowed for display.
> +<BR>
> +The page <TT>controlled/any</TT> (or any other page in the directory not named in <TT>.access_gate</TT>) will be allowed for any user logged in via <I>UserDB</I>.</UL><OL>
> +<LI>If the Variable <TT>MV_USERDB_REMOTE_USER</TT> is set (non-zero and non-blank), any user logged in via the UserDB feature will receive access to all pages in the directory. NOTE: If there is a <TT>.access_gate</TT> file, it overrides this.
> +<LI>If the variables <TT>MV_USERDB_ACL_TABLE</TT> is set to a valid database identifier, the UserDB module can control access with simple ACL logic. See USER DATABASE. NOTE: If there is a <TT>.access_gate</TT> file, it overrides this. Also, if <TT>MV_USERDB_REMOTE_USER</TT> is set, this capability is not available.</OL>
> +</DIV>
> +<DIV CLASS="footer">
> +<DIV CLASS="navigate">
> +<P ALIGN="Center"><A HREF="icadvanced_11.html">Parent Topic</A> | <A HREF="icadvanced_11.html">Previous Topic</A> | <A HREF="icadvanced_13.html">Next Topic</A> <BR><A HREF="../index.html" TARGET="_top">Documentation Index</A></P>
> +</DIV>
> +</DIV>
>
> -=over 4
> -
> -=item
> -
> -The page controlled/foo is only allowed for the logged-in user
> -B<flycat>.
> -
> -The page controlled/bar is allowed for the logged-in user
> -B<flycat>, or if the scratch variable allow_bar is set to a
> -non-blank, non-zero value.
> -
> -The page controlled/baz is always allowed for display.
> -
> -The page controlled/any (or any other page in the directory not
> -named in .access_gate) will be allowed for any user logged in via
> -I<UserDB>.
> -
> -=back
> -
> -=over 4
> -
> -=item 2.
> -
> -If the Variable MV_USERDB_REMOTE_USER is set (non-zero and
> -non-blank), any user logged in via the UserDB feature will receive
> -access to all pages in the directory. NOTE: If there is a
> -.access_gate file, it overrides this.
> -
> -=item 3.
> -
> -If the variables MV_USERDB_ACL_TABLE is set to a valid database
> -identifier, the UserDB module can control access with simple ACL
> -logic. See USER DATABASE. NOTE: If there is a .access_gate file, it
> -overrides this. Also, if MV_USERDB_REMOTE_USER is set, this
> -capability is not available.
> -
> -=back
> +</BODY>
> +</HTML>
> _______________________________________________
> docs mailing list
> docs@icdevgroup.org
> http://www.icdevgroup.org/mailman/listinfo/docs
--
Mike Heins
Perusion -- Expert Interchange Consulting http://www.perusion.com/
phone +1.513.523.7621 <mike@perusion.com>
Friends don't let friends use Outlook. -- Bob Blaylock