pass / file:/u/john/welcome.html pass /* file:/u/john/public/* fail *The first line maps the root document onto a specific document about the server, and accepts it. (see etiquette about the welcome page)
The second line maps all document names onto filenames in a particular directory and accepts them.
The third line disallows access to all other documents. (There won't be in any in this case because of the mapping, but its wise to put in for later).
map / /tnotes/welcome.html map /tnotes/* file:/u/john/public/* map /seminars/* file:/u/jane/seminars/* pass file:/u/john/public/* pass file:/u/jane/seminars/*.html fail *The first line maps the root document onto a specific document about the server. Because it is "map and not "pass", it DOESN'T accept it but passes it on for futher mapping by lines futher down.
The second line maps all document names starting with /tnote/ onto filenames in a particular directory where john maintains the technical notes. If someone else takes over the technical notes, we can change this. Here we are starting to distinguish between document names and file names. This can be carried much further if necessary, but one level of mapping is enough to allow for changes of administration of different areas.
The third line separately maps the seminar information into Jane's directory.
The fourth and fifth line enable access to anything in John's "public" directory, and any .html file in Jane's "seminar" directory tree. Note here that the * maps to any sequence INCLUDING SLASHES so all files in any subdirectory of /u/jane/seminars will be enabled so long as they end in .html.
The bottom line will pick up for example any attempt to use the server to access non-html files in Jane's seminars directory.
map /* wais://* pass wais://* fail *