Another way to do this is to create a URL mapping to a central directory that all of your users can modify.With this system, clients can access your server with a certain URL that the server recognizes as a public information directory. For example, suppose you choose the prefix ~ and the directory public_html. If a request comes in for http://www.netscape.com/~jdoe/aboutjane.html, the server recognizes that ~jdoe refers to a users' public information directory. It looks up jdoe in the system's user database and finds Jane's home directory. The server then looks at ~/jdoe/public_html/aboutjane.html. To configure your server to use public directories, you need to choose a user URL prefix. The usual prefix used is ~ because it's a character that is rarely used. Next, you need to choose the subdirectory where the server looks for user home directories. A typical directory is public_html. The server needs to know where to look for a file that lists users on your system. The server uses this file to determine valid user names and to find their home directories. You can use the system password file for this, which means the server uses standard library calls to look up users. Or, you can create another user file to use to look up users. You can specify that user file with an absolute path. Each line in the file should have this structure (the elements in the /etc/passwd file that aren't needed are indicated with *):
username:*:*:groupid:*:homedir:*You also have the option of loading the entire password file on startup. If you choose this option, the server loads the password file into memory when it starts, making user lookups much faster; if you have a very large password file, however, this can use too much memory. Finally, you can choose a configuration template that the server uses so that you can control what is allowed from public information directories. This can prevent users from creating symbolic links to information you don't want made public, and so on. To set up user directories, do the following:
To enable remote file manipulation, do the following from the Server Manager:
products
, another called people
, and so on. It's often helpful to let clients access an overview (or index) of these directories.
There are two ways the server can do this:index.html
, which is a file you create and maintain as an overview of the directory's contents. You can specify any file as an index file for a directory. This means you can also use CGI programs as an index if CGI is activated.
/info/movies
in the field.)
:LASTMOD:
if you want to include the last-modification date.
©
) you enter will be expanded when
you edit the footer again. If you do edit it again, be sure to re-expand the
entities.
*.gif
).
To apply a configuration style, do the following:/*
after the directory, all of
the directory's contents will have the configuration style applied.