home *** CD-ROM | disk | FTP | other *** search
- from the server. This is even if you're
- reloading the same page, and for every image on the page (if
- they come from a protected directory). As you can imagine, this
- slows things down a little. The amount that it slows things
- down is proportional to the size of the password file, because
- it has to open up that file, and go down the list of users
- until it gets to your name. And it has to do this every time a
- page is loaded.</p>
-
- <p>A consequence of this is that there's a practical limit to
- how many users you can put in one password file. This limit
- will vary depending on the performance of your particular
- server machine, but you can expect to see slowdowns once you
- get above a few hundred entries, and may wish to consider a
- different authentication method at that time.</p>
- </section>
-
- <section id="whatotherneatstuffcanido"><title>What other neat stuff can I
- do?</title>
- <p>Authentication by username and password is only part of the
- story. Frequently you want to let people in based on something
- other than who they are. Something such as where they are
- coming from.</p>
-
- <p>The <directive module="mod_access">Allow</directive> and
- <directive module="mod_access">Deny</directive> directives let
- you allow and deny access based on the host name, or host
- address, of the machine requesting a document. The
- <directive module="mod_access">Order</directive> directive goes
- hand-in-hand with these two, and tells Apache in which order to
- apply the filters.</p>
-
- <p>The usage of these directives is:</p>
-
- <example>
- Allow from <var>address</var>
- </example>
-
- <p>where <var>address</var> is an IP address (or a partial IP
- address) or a fully qualified domain name (or a partial domain
- name); you may provide multiple addresses or domain names, if
- desired.</p>
-
- <p>For example, if you have someone spamming your message
- board, and you want to keep them out, you could do the
- following:</p>
-
- <example>
- Deny from 205.252.46.165
- </example>
-
- <p>Visitors coming from that address will not be able to see
- the content covered by this directive. If, instead, you have a
- machine name, rather than an IP address, you can use that.</p>
-
- <example>
- Deny from <var>host.example.com</var>
- </example>
-
- <p>And, if you'd like to block access from an entire domain,
- you can specify just part of an address or domain name:</p>
-
- <example>
- Deny from <var>192.101.205</var><br />
- Deny from <var>cyberthugs.com</var> <var>moreidiots.com</var><br />
- Deny from ke
- </example>
-
- <p>Using <directive module="mod_access">Order</directive> will let you be
- sure that you are actually restricting things to the group that you want
- to let in, by combining a <directive module="mod_access">Deny</directive>
- and an <directive module="mod_access">Allow</directive> directive:</p>
-
- <example>
- Order deny,allow<br />
- Deny from all<br />
- Allow from <var>dev.example.com</var>
- </example>
-
- <p>Listing just the <directive module="mod_access">Allow</directive>
- directive would not do what you want, because it will let folks from that
- host in, in addition to letting everyone in. What you want is to let
- <em>only</em> those folks in.</p>
- </section>
-
- <section id="moreinformation"><title>More information</title>
- <p>You should also read the documentation for <module>mod_auth</module>
- and <module>mod_access</module> which contain some more information
- about how this all works.</p>
- </section>
- </manualpage>
-
- <?xml version="1.0" encoding="UTF-8" ?>
-
- <metafile>
- <basename>auth</basename>
- <path>/howto/</path>
- <relpath>..</relpath>
-
- <variants>
- <variant>en</variant>
- <variant htmlonly="yes">ja</variant>
- </variants>
- </metafile>
- <?xml version='1.0' encoding='UTF-8' ?>
- <!DOCTYPE manualpage SYSTEM "../style/manualpage.dtd">
- <