This tutorial is not a web/html primer and assumes that you already know
how the process of "web surfing" is accomplished (i.e. a browser requests a page from a server which
then returns the page to be viewed), what HTML tags are and how to use them.
If you are not familiar with these concepts please read a basic web/html primer.
Using this feature is easy.
All you need to do is specify a valid username and password for a given URL prefix (web site address prefix).
Detailed instructions on how you do this are in the next section below.
To setup password protected indexing for part of your site simply
log in to your account,
go to the
page and use the password protected areas link.
When the wizard appears list the "authorization specification" for each password protected area of your site,
one per line (browser wrapping may be ignored),
and then press the
button to save your changes.
Each authorization specification consists of a "URL mask" and a valid username and password to access pages which match the mask.
Here are a couple quick examples:
Also, it is valid to have no user name and password information:
The URL mask is simply a standard web address, but may contain the common wildcards
"*" and "?" to make it
match more than one web address.
The "*" will match any number of any character and
the "?" will match any single character.
Non-wildcard characters are matched without regard to case (case-insensitive).
URL masks which do not begin with "http://"
are treated as if they begin with "*".
Because of this it is recommended that you include the "http://"
in your URL masks.
The URL mask is typically followed by a valid user name and password, as shown in the example above.
Any time our spider (indexer) requests a page which has a matching URL mask, the user name and password will be provided
to that server.
If a matching URL mask has no associated user name and password, then the page is assume to be public and not require any authorization.
Your visitors will never see this information, but be sure to specify your server in the URL mask
otherwise your user name and password will be sent to someone else's server!
When determining which authorization specification to apply, the entire list is considered
and the last matching authorization specification is used. This allows convenient expression
of "include everything but..." logic. For example, if everything in your
"http://example.com/members/" directory is password protected
except pages in the
you can use the following: