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: How the Index to WN User's Guide Works
Matching lines:
- http://host/docs/search=context?content-type
- Title: User's Guide for the WN Server
Matching lines:
- Title: An Overview of the WN server
Matching lines:
- <http://host/dir/search=title> the server will
- <http://host/dir/search=context> where
- <http://host/dir/foo;lines=20-30> and
- Title: Installation and Setup of WN
Matching lines:
- it is relatively light (a few thousand hits per day) and the host on
- 2.4 Your Hostname: What's in a Name?
- its own hostname. Ideally, in my opinion, the server should do nothing
- with its hostname and not even need to know it. This is not possible for
- protocol requires the server to pass its hostname to CGI programs in
- hostname. These are the only places WN uses hostname.
- For most cases then, WN only uses it hostname when a redirection
- So how does WN know its hostname? When you run the
- #define WN_HOSTNAME
- gethostbyaddr(3)
- wn/vhost.h which you edit to set up the correspondence
- http://localhost/docs/index.html
- lookup to do for the remote host. The two most common formats
- last field of each log entry. If virtual hosting is not being used
- Value assigned this virtual host by the maintainer (omitted if virtual
- hosting is not used).
- Title: Creating your WN data directory
Matching lines:
- Owner=mailto:webmistress@host.edu
- Owner=mailto:you@host.edu
- http://host/dir1/dir2/, this will be translated to a request
- for http://host/dir1/dir2/index.html.
- which no valid password was given, and requests from an invalid host for
- files limited to certain hosts. The lines:
- No-Such-File-URL=http://host/dir/nosuch.html
- Access-denied-URL=http://host/dir/noaccess.html
- invalid host. The last line specifies a file to be sent when a password
- Title: Security on the WN Server
Matching lines:
- purported client on a remote host, and (2) local, from a user with an
- account on the server host.
- alteration of) files on the host system. Programs run on the server with
- host. Which user is determined when you run the
- hostile user could write a
- potentially hostile users on the same server. I would also strongly
- advise against allowing potentially hostile
- program can alter or destroy log files. A hostile authorization module
- restriction by hostname or IP address. It is not impossible to spoof a
- easier to use a counterfeit hostname. For this reason I would suggest
- using IP addresses rather than host names in
- always put your host and domain name in the realm. This may at least
- password contains a different hostname than the one in the URL they are
- If no potentially hostile users can create documents which can be served
- This permits users on the server host to have and control their own
- Title: Setting Up Searches on the WN Server
Matching lines:
- <http://host/dir/search=title>
- "http://host/dir/search=title" and which uses the
- <http://host/dir/search=keyword>
- <http://host/dir/search=synopsis>
- <http://host/dir/search=field3>
- <http://host/dir/search=context>
- <http://host/dir/search=grep>
- <http://host/dir/search=line>
- <http://host/dir/foo;search=context>
- <http://host/dir/foo;search=grep>
- with URLs like "<http://host/dir/search=context>"
- <http://host/dir/foo;search=list>
- something like http://host/dir/search=index.
- Title: Parsed Text and Server Side Includes on the WN server
Matching lines:
- to certain hosts, or to clients providing an appropriate
- Cookie header, the client hostname, or the client IP
- <!-- #if referer !~ "my.host.edu" -->
- accessing this document via any link which is not on the host
- my.host.edu.
- <!-- #if hostname =~ "\.uk$" -->
- a UK host will automatically be redirected to the specified URL, the
- is fully qualified, like "http://host/path/foo". However,
- header, user-agent, hostname, etc. For example, if the file
- Hosts not listed in the file "secret/access" can't look at it, so why
- "Restricted Local Stuff" only to clients on hosts
- <!-- #if hostname =~ "\.uk$" && accessfile="secret/access" -->
- http://host/path/foo;meta
- Title: User Defined Fields on the WN server
Matching lines:
- http://host/dir/search=field3
- Title: Ranges on the WN server
Matching lines:
- http://host/dir/foo;lines=20-30
- http://host/dir/foo;bytes=256-1024
- http://host/dir/foo;bytes=256-
- http://host/dir/foo;bytes=-1024
- Title: Limiting Access to Your WN Hierarchy
Matching lines:
- access by hostname or IP address and you can restrict access to users
- 10.1 Access Control Files: Limiting Access by Hostname or
- allows access to one host. To allow access to all machines in the
- more secure than using the hostnames. There are two line formats for IP
- #define NO_DNS_HOSTNAMES
- #define NO_DNS_HOSTNAMES
- causes WN never to convert IP addresses to hostnames.
- causes immediate denial of access to any matching host. The first
- matching line (with or without leading '!') for a host is
- Access-denied-URL=http://host/dir/foo.html
- "http://host/dir/foo.html" or "/dir/foo.html".
- Authorization-realm=myrealm@host.domain
- realm. For security reasons it is a good idea to put your host and
- hostname than the one in the URL they are trying to access.
- Title: Users' Hierarchies and Personal Home Pages on the WN server
Matching lines:
- on a single host and will use a different data root for different IP
- "http://hostname/~john/foo.html" to request a document in a
- "http://hostname/foo.html" with root directory
- "http://hostname/people/john/foo.html" would result in the
- then the URL "http://hostname/~bob/foo.html" will be
- then "http://hostname/people/john/foo.html" will be
- local server host. To do this, specify a lookup table entry consisting
- "otherhost", you can specify the lookup table entry like
- jim::http://otherhost/~jim
- "http://hostname/people/jim/path/file.html" to your server,
- "http://otherhost/~jim/path/file.html".
- are actually on that host.
- Title: Multi-homed or Virtual Servers on the WN server
Matching lines:
- Many systems allow multiple IP addresses for a single host. For systems
- each IP address to which your host responds. Sometimes this is referred
- to as "virtual hosts" or a "multi-homed" server since when combined with
- hosts. Unfortunately, I cannot help you in configuring your system to
- 12.1 One Server per Virtual Host
- There are two ways to have multiple virtual hosts. Assuming
- gethostbyname(3)
- #define USE_VIRTUAL_HOSTS"
- the server for each host name is running at all times and thus using
- different log file for each host, while the method below uses only one
- host.
- Hosts
- changes the document root as appropriate based on the IP address or host
- #define USE_VIRTUAL_HOSTS".
- list of the virtual hosts or you can build this list into the compiled
- If you have only a few virtual hosts and you don't anticipate adding new
- 12.2.1 Using a Virtual Hosts List
- You can either compile in the list of virtual hosts or keep this list
- To use a virtual host file you must uncomment the line containing "
- #define VIRTUAL_HOSTS_FILE"
- Maximum number of matches per file exceeded.
- Title: WN Utility Programs
Matching lines:
- "http://hostname/dir/file". If there is no
- also can extract the entries for each virtual host of a
- virtual host with
- /wn/vhost.h to contain:
- #ifdef USE_VIRTUAL_HOSTS
- vhostlist[][4] =
- host with DNS name virtual2.com. If you have used the empty
- string in place of nicknames in the file wn/vhost.h the
- virtual hosts are numbered consecutively in the order they are listed,
- the log entries for the second virtual host.
- option gives the verbose form of log entries for specified virtual host.
- Cache-module=redir http://host/dir/foo.html
- redirected to a request for http://host/dir/foo.html.
- Cache-module=redir http://host/dir/
- then a request for http://this_host/this_dir/whatever.html
- will be redirected to http://host/dir/whatever.html. These
- Title: WN Auxiliary Modules
Matching lines:
- http://host/dir/search=index
- Title: Clickable Images and Imagemap files on the WN Server
Matching lines:
- default http://webhost/dir/default.html
- rect http://webhost/dir/rect.html 20,20 70,100
- circle http://webhost/dir/circle.html 70,70 70,100
- poly http://webhost/dir/triangle.html 10,20 70,100 5,150
- point http://webhost/dir/point1.html 10,20 70,100
- point http://webhost/dir/point2.html 100,110 80,5
- nocoords http://webhost/dir/message.txt
- http://remote_host/dir/rect.html
- "http://remote_host/dir/rect.html" is primarily used to link
- to a document on a remote host. On seeing this the server sends an
- "http://local_host/dir/rect.html". Any URL specified in a
- local local host and the path is assumed relative to the WN root
- http://host/~user/ type URLs.
- Title: Using CGI Programs on the WN Server
Matching lines:
- client's hostname, IP address, user-agent, or the "referer", the document
- print "REMOTE_HOST = $ENV{REMOTE_HOST}<br>\n";
- it prints out the client's hostname, user agent and the URL of the
- http://host/foo.html is requested this will cause the
- Title: Configuration File for the WN Package
Matching lines:
- #define MAINTAINER "mailto:webmaster@your.host"
- #define WN_HOSTNAME ""
- * You may enter your fully qualified host name here. If the default
- * value of "" is used WN will get the default hostname from your system.
- * WN will attempt to use the gethostbyname() system call to find the
- * CGI scripts on your host. This will enhance security but will,
- /* #define NO_DNS_HOSTNAMES */
- * Uncomment this if you do not wish the server to look up DNS hostnames
- * files and never use hostnames. This is more efficient and more
- /* #define CHECK_DNS_HOSTNAMES */
- * lying about its DNS hostname. Leave it commented for a slight
- /* #define USE_VIRTUAL_HOSTS */
- /* #define VIRTUAL_HOSTS_FILE "/full/path/virtual_hosts" */
- * Uncomment these to use a virtual hosts file. See docs/multi.html
- * with the URL syntax like http://hostname/~user/. Read the chapter
- * but use "/~" to make http://hostname/~user/ work. This appears to
- * returned to requests from remote hosts. WN is slightly more efficient
- Title: Command Line Options for the WN Server
Matching lines:
- -h hostname -- Set
- hostname
- hostname. This is only used for a few
- address obtained from the UNIX gethostbyname(3)
- hostname of the client for logging purposes. If the
- IP address in the log instead of the host name. For example
- but should use IP addresses rather than host names in log
- -V virtual_host_file --
- Set file name which contains the list of virtual hosts
- The file "virtual_host_file" should be the name
- of the file containing the list of "virtual hosts" and their
- file is one line per virtual host. Each such line should have the
- hostname IP_address root_path
- myhost.school.edu 111.222.333.444 /var/wn
- In particular the hostname should be the fully qualified domain name.
- If the virtual host file is changed you will need to restart the
- Title: Index File Directives for the WN Server
Matching lines:
- determine access privileges (by hostname or IP address) for this
- Access-denied-URL=http://host/dir/foo.html
- http://host/dir/ will result in serving the document
- with no DNS hostnames only IP addresses in the log entries.
- hostname of the client for logging purposes. If the
- IP address in the log instead of the host name. For example
- log format, but should use IP addresses rather than host
- No-Such-File-URL=http://host/dir/foo.html
- Owner=mailto:maintainer@host
- The "mailto:maintainer@host" may be replaced with a URL
- like http://host/dir/search=index. Two simple examples
- So when http://host/path2/foo.html is requested
- Redirect=http://host/path/bar
- "http://host/path/bar". This means that the value of a
- Refresh=30; URL=http://host/path/foo
- http://host/path/foo is loaded. This can be used to
- Title: Parsed Document Syntax for the WN Server
Matching lines:
- #if hostname
- -- Match client's hostname
- <!-- #if hostname =~ "regexp" -->
- <!-- #if hostname file= "foo" -->
- hostname of the client (in the first case) or if the file
- #if host_header
- -- Match server's virtual hostname from client's HTTP Host header
- <!-- #if host_header =~ "regexp" -->
- contents of the HTTP "Host:" header supplied by the
- URL requested with the "http://host" part having been
- determine access privileges (by hostname or IP address) for this text
- <!-- #if hostname =~ "\.uk$" -->
- from a uk host will automatically be redirected to the
- before the "#if hostname" line or any blank lines
- <!-- #if hostname =~ "\.uk$" -->
- line is fully qualified, like "http://host/path/foo".
- Title: CGI and other Environment Variables for the WN Server
Matching lines:
- HTTP_HOST
- Contains the contents of the "Host:" header supplied by
- the client. This should contain the one of the aliases for the host
- on which the server is running. It should be the hostname from the
- "http://www.serverhost.com:8000/foo.html" should supply
- "www.serverhost.com" in this header. Many browsers do
- URL "http://host/dir/foo.cgi/stuff1/stuff2/stuff3"
- "http://host/dir/foo.cgi/stuff1/stuff2/stuff3" would
- "http://host/dir/foo.cgi/stuff1/stuff2/stuff3?dingbat"
- REMOTE_HOST
- Contains the hostname of the client or proxy making the request, if
- #define NO_DNS_HOSTNAMES"
- hostname and REMOTE_HOST will contain the IP address.
- "http://host/dir/foo.cgi/stuff1/stuff2/stuff3" would
- "http://host/dir/foo.cgi/stuff1/stuff2/stuff3" would
- Contains the name of the "virtual host" currently being accessed, if
- virtual hosting is in use. Otherwise it
- contains the name of host on which server is running. The value of
- HTTP_HOST if the client
- supports the "Host header:". Otherwise it will be
- Maximum number of matches per file exceeded.
- Title: Creating User Home Pages for the WN Server
Matching lines:
- Locator") is made up from the name of your host and your user name. For
- Title: Configuration Macros for WN
Matching lines:
- hostname, (something like "http://hostname.edu/" with no
- host. This will enhance security but will, of course, decrease
- #define NO_DNS_HOSTNAMES
- If this is set to TRUE the server will not use hostnames in your
- CGI programs will get the hostname and also
- hostnames in them, just IP addresses.
- "/~" to make "http://hostname/~user/" work.
- #define USE_VIRTUAL_HOSTS
- If defined to the full path to the file of virtual hosts,
- wnsd will support multi-homed or virtual hosts as described
- #define VIRTUAL_HOSTS_FILE
- Full path to virtual hosts file. See the section "
- Using a Virtual Hosts List
- #define WN_HOSTNAME
- default hostname from your system. If you supply a name it should be a
- gethostbyname(3)
- Title: Changelog for WN
Matching lines:
- hosts file to be read when syslogging was in use.
- virtual host used. The user/group <--> virtual host match up set
- in the virtual hosts file. The documentation has been updated to
- virtual hosts with suexec.
- Virtual hosts now allow you to turn off the possbility of user
- words http://host/foo.html;meta does the same thing that
- http://host/foo.html;info has always done. I bet the "info"
- Fixed bug in vhost.h (missing '=').
- Added support for virtual host nicknames which will be used
- http://host/foo;bytes=111-222 will now give the returned range a
- omit host name and only use IP address. (reported by D. Capshaw)
- since is in the index file. So when http://host/foo.html is requested
- now work properly with virtual hosting. I.e. they default to
- the hostname specified in a Host: header rather than the compiled
- in hostname.
- Fixed bug in wn/prequest.c that caused virtual hosting to work
- improperly when a URL with an IP number instead of a hostname
- Fixed bug in wn/prequest.c so virtual host name comparison is
- http://host/cgi-bin/dir/foo are made. CGI scripts must be in a
- like "http://host/~user/". (reported by H. MacEwan and U. Pfeifer).
- Maximum number of matches per file exceeded.
- Title: Quick start
Matching lines:
- http://yourhost/
- or http://yourhost:8080/ if you used the -p 8080 option.
- http://yourhost/docs/manual.html
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]