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:
- Title: Installation and Setup of WN
Matching lines:
- 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
- Title: Security on the WN Server
Matching lines:
- 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
- password contains a different hostname than the one in the URL they are
- Title: Parsed Text and Server Side Includes on the WN server
Matching lines:
- Cookie header, the client hostname, or the client IP
- <!-- #if hostname =~ "\.uk$" -->
- header, user-agent, hostname, etc. For example, if the file
- <!-- #if hostname =~ "\.uk$" && accessfile="secret/access" -->
- 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
- 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.
- 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:
- "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
- "http://hostname/people/jim/path/file.html" to your server,
- Title: Multi-homed or Virtual Servers on the WN server
Matching lines:
- hostname IP_address root_path vhost_nickname user group flag
- In particular the hostname should be a fully qualified domain name.
- the hostname and port it is trying to access) the WN server will
- the hostnames that corresponds to this IP address, and a nickname to use
- The hostname in these lines is used by the server in only two
- Title: WN Utility Programs
Matching lines:
- "http://hostname/dir/file". If there is no
- Title: Using CGI Programs on the WN Server
Matching lines:
- client's hostname, IP address, user-agent, or the "referer", the document
- it prints out the client's hostname, user agent and the URL of the
- Title: Configuration File for the WN Package
Matching lines:
- #define WN_HOSTNAME ""
- * value of "" is used WN will get the default hostname from your system.
- /* #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
- * with the URL syntax like http://hostname/~user/. Read the chapter
- * but use "/~" to make http://hostname/~user/ work. This appears to
- Title: Command Line Options for the WN Server
Matching lines:
- Title: Index File Directives for the WN Server
Matching lines:
- determine access privileges (by hostname or IP address) for this
- with no DNS hostnames only IP addresses in the log entries.
- hostname of the client for logging purposes. If the
- 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
- -- Match server's virtual hostname from client's HTTP Host header
- determine access privileges (by hostname or IP address) for this text
- <!-- #if hostname =~ "\.uk$" -->
- before the "#if hostname" line or any blank lines
- <!-- #if hostname =~ "\.uk$" -->
- Title: CGI and other Environment Variables for the WN Server
Matching lines:
- on which the server is running. It should be the hostname from the
- 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.
- Title: Configuration Macros for WN
Matching lines:
- hostname, (something like "http://hostname.edu/" with no
- #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 WN_HOSTNAME
- default hostname from your system. If you supply a name it should be a
- Title: Changelog for WN
Matching lines:
- the hostname specified in a Host: header rather than the compiled
- in hostname.
- improperly when a URL with an IP number instead of a hostname
- on virtual hostname (see docs/appendixC.html).
- swn when hostname was specified in config.h or on command line.
- If the server gets its hostname from config.h or the command line
- local hostname specified by #define WN_HOSTNAME in config.h (thanks
- WN_HOSTNAME need no longer be set in config.h. It has been moved to
- without the -h option. I should point out the hostname is almost never
- with only the hostname. You would need to change it if, for example,
- The NONET #define is gone and there is now a #define NO_DNS_HOSTNAMES
- be no hostnames in your log file, just IP addresses. This will reduce
- get the hostname and also that your access files cannot have hostnames
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]