Version 2.5.0
[Table of Contents]
WN Documentation Search Results -- Matches
You may select a new search term and repeat your search:
Matches
Here are the matching lines in their respective document sections.
Select one of the highlighted words in the matching lines below to jump
to that point in the document.
- Title: User's Guide for the WN Server
Matching lines:
- Chapter 3: Creating Your WN Data
- Database Modules
- WN Specific Database
- Title: An Overview of the WN server
Matching lines:
- keep this information in small databases, one for each directory in the
- database files (named index.cache by default), but this
- database or if explicit permission to serve all files in
- /dir. This database also provides other security functions.
- file in the data hierarchy should be orthogonal to security restrictions
- The index.cache database file has a number of other
- maintainer also has the option of adding his own fields to this database
- So how are the index.cache databases created? Their format
- database. A field search could then produce all documents by a given
- database entry for a file may be inserted.
- Title: Installation and Setup of WN
Matching lines:
- wnroot of your data hierarchy.
- will be asked the complete path name of your data directory. You will
- data and should not own or have have write permission. In particular
- index.cache database file described in the chapter "
- Creating Your WN Data Hierarchy" of
- on logging or use a different data directory. Some inetd(8)
- symbolic link in your wnroot data directory to the
- subdirectories to your data directory temporarily.
- Title: Creating your WN data directory
Matching lines:
- Creating your WN data directory
- Creating Your WN Data Directory
- In each directory of your data hierarchy you create a file called
- small database called index.cache containing information
- The index.cache database has a number of other functions
- the index.cache database file. Simply running
- wndex to recursively descend your data hierarchy using all
- Title: Security on the WN Server
Matching lines:
- allow any data sent by a client even to be written to a temporary disk
- granted by the maintainer. The WN server keeps a small database
- in each directory of its data hierarchy which contains information about
- database.
- Note: For more information on these database files the chapter
- WN Data Directory" in this guide.
- database there granting illicit access to some documents on the server
- There are several defenses against such a counterfeit database and we
- directory database files (these files have the default name
- access or is outside the server data hierarchy.
- internally accessing any file which is not in your data directory. If
- of your data hierarchy has all the permissions of the user id under which
- index.cache file in your data hierarchy.
- index.cache files for another part of your server's data
- the index.cache database files. The server will not
- involved an attack by overflowing an internal buffer with data provided
- defended against this in WN code. All copying of data supplied
- by the client and most copying of data read from the
- which was designed precisely to deal with this threat. Excess data which
- would overflow is discarded so buffers may contain truncated data, but
- Maximum number of matches per file exceeded.
- Title: Setting Up Searches on the WN Server
Matching lines:
- very slow with 1000 files spread out in a data hierarchy. For that you
- Title: Parsed Text and Server Side Includes on the WN server
Matching lines:
- for example, then it will return meta data about the resource
- Here is the meta data returned
- Title: Filters on the WN server
Matching lines:
- is in the handling of POST or PUT data. A
- data provided by the client on its UNIX
- POSTed data by opening and reading the temporary file
- containing this data. The name of this file changes with each request,
- depending on the method used to submit the data.
- Title: Limiting Access to Your WN Hierarchy
Matching lines:
- access or is outside the server data hierarchy.
- causes a UNIX NDBM database to be created or used instead of
- number of password entries. Depending on your system, the database may
- -D option. To create a new database you must remove or
- filename" for an NDBM database.
- uses an MD5 hash of the password, the realm, and random data to encode
- the password. The realm and random data are created when
- database "wnpasswd.dir" and "wnpasswd.pag"
- Title: Users' Hierarchies and Personal Home Pages on the WN server
Matching lines:
- set the data hierarchy based on information in the
- on a single host and will use a different data root for different IP
- system password file and changes the root data directory to
- equivalent of a URL request for "/foo.html" with a data root
- A second method of establishing an alternate data hierarchy does not use
- and their corresponding data hierarchy directories.
- translated to a request for "/foo.html" with the data root
- data directory. Of course, the name need not be the name of a user. One
- translated to a request for "/foo.html" with root data
- new data hierarchy root.
- When you use the table lookup method to retarget data root directories of
- the user's data root directory. For example, if user "jim"
- has a data root that is accessed as "~jim" on
- Title: Multi-homed or Virtual Servers on the WN server
Matching lines:
- with this capability it is possible to use a different data hierarchy for
- data hierarchies for each IP address if you run the stand-alone version
- use the root data directory you specified for that host name. Similarly
- server will use the root data directory corresponding to
- the server will use the first root data directory whose IP number matches
- { "virtual1.com" , "123.123.121.1", "/var/data1", "nickname1", NULL, NULL, NULL },
- { "virtual2.com" , "123.123.121.1", "/var/data2", "nickname2", "usr2", "grp2", "1" },
- { "another.ip.com", "123.123.123.2", "/var/data3", "nickname3", "usr3", "grp3", "1" },
- { "virtual2.com", "123.123.121.1", "/var/data2", "nickname1" },
- the corresponding data root instead of "/var/data1", one of
- addresses listed in this file then the server will use the default data
- Title: WN Utility Programs
Matching lines:
- multi-homed server which uses different data roots
- { "virtual1.com" , "123.123.121.1", "/var/data1", "nickname1" },
- { "virtual2.com" , "123.123.121.1", "/var/data2", "nickname2" },
- { "another.ip.com", "123.123.123.2", "/var/data3", "nickname3" },
- Title: WN Auxiliary Modules
Matching lines:
- authorization (authentication) or indexed searches or database access.
- 14.1 Database Modules
- database containing characteristics of that directory and the files
- database. It is permissible to follow "foo" in this line
- database. To use such a database interface called "bar", in
- The program "bar" should be an interface to your database.
- which might be returned by the database or to have an
- Title: Using CGI Programs on the WN Server
Matching lines:
- supports a variety of methods of searching your data including by title,
- Title: Default Index Cache Files
Matching lines:
- files are useful is to serve data from read-only media such as
- cache file must be in a directory in the WN data
- Title: Configuration File for the WN Package
Matching lines:
- * Enter the complete path of your root data directory here.
- * data or 512 lines of text are sent. For
- * methods of allowing alternate data hierarchies. This is the way
- * you permit users to have data hierarchies in their home directories
- Title: Format of index.cache file for WN
Matching lines:
- Cache-module cachemod /* Cache data base module */
- File-module filemod /* File data base module */
- Title: Command Line Options for the WN Server
Matching lines:
- outside the server data hierarchy.
- Title: Index File Directives for the WN Server
Matching lines:
- Specifies that the index.cache databases in the
- own module to handle authorization. Data is passed via
- Specify program to be used as interface to database for
- provides a mechanism to use a real database rather than the file
- require reading the entire database.
- Specify program to be used as interface to database for obtaining
- mechanism to use a real database rather than the file
- own module to handle PUT authorization. Data is placed in
- to create a new index.cache database file. Likewise
- recursively descends the data hierarchy and must know for each
- case the POSTed data will be in placed in a
- your program. The PUT data will be in placed in a
- bar to be in the served data hierarchy and it
- Title: Parsed Document Syntax for the WN Server
Matching lines:
- taken relative to the WN data hierarchy root. The format of
- Title: CGI and other Environment Variables for the WN Server
Matching lines:
- data.
- the WN root data directory. For example, the URL
- Contains the path to your WN root data directory relative to
- Contains the path to the temporary file containing the data sent by
- Contains the path to the temporary file containing the data sent by
- D.3 WN Specific Database Variables
- with external databases.
- WN_KEY is used in conjunction with external databases
- Title: Creating User Home Pages for the WN Server
Matching lines:
- Data Directory" in this guide. Neither of these chapters is too
- Title: Configuration Macros for WN
Matching lines:
- Creating Your WN Data Directory" in
- Complete path of your root data directory.
- Title: Changelog for WN
Matching lines:
- Modified server so that data reflected to client in
- the clients query data returned by <!-- #query -->.
- Data returned from environment variables is NOT sanitized.
- This is sent if POST data is larger than 5 meg (MAXPOST in config.h).
- and keep username/password pairs in an ndbm data base. The
- data directory.
- Increased the default maximum size of POST data from 2 meg. to
- data root directory for each. Secondly the server now supports
- Fixed bug in send.c which caused rewriting of same data when there
- HTTP_POST_FILE and contains the path to a file containing the data
- Added minimal support for different data roots corresponding to different
- is now reset each time 1024 lines of text or 128K of binary data have
- Title: Quick start
Matching lines:
- you have designated as your data root. Add other HTML files if you
- 4. In your data root directory create a file named "index" that
- Now in that directory run the command "wndex". This creates a data
- directory (your data root directory). If you used the line
- data root directory to /path/2/WN_src/docs/ and then use the URL
- Title: GNU Public License
Matching lines:
- TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
WN version 2.5.0
Copyright © 1998-2005 John Franks
<john@math.northwestern.edu>
licensed under the GNU Free Documentation License
Last modified: Sat June 18 2005
[Table of Contents]