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: An Overview of the WN server
Matching lines:
- a document to different clients. By adding simple
- to clients, based on such things as the client's domain name, IP address,
- utility which uncompresses it. Then the client is served the
- Title: Installation and Setup of WN
Matching lines:
- clients often implement redirection so that it cannot handle relative but
- Try it with your favorite HTTP client. The
- From the client's cookie header.
- From the client's X-Forwarded-For header.
- Title: Creating your WN data directory
Matching lines:
- There are three situations when the client request will be denied but for
- file specify URL's to which clients are redirected when a non-existent
- Title: Security on the WN Server
Matching lines:
- which this document addresses separately: (1) external, from a client or
- purported client on a remote host, and (2) local, from a user with an
- allow any data sent by a client even to be written to a temporary disk
- The basic philosophy of WN security is that by default no client
- client supplied headers. If your needs can be met with these features
- by the client (in
- is read from the client and put in a temporary file on disk. Then the
- no publicly available clients currently support it. It is experimental,
- because I have no client to test it and hence it has barely been tested.
- used whenever an authentication module is used, is to notify the client
- same password/username combination will be valid, so the client need not
- by the the client in such a way that the (attacking) client could supply
- by the client and most copying of data read from the
- Title: Setting Up Searches on the WN Server
Matching lines:
- line. You can, of course, insert the client supplied search term by use
- Title: Parsed Text and Server Side Includes on the WN server
Matching lines:
- to certain hosts, or to clients providing an appropriate
- allows alternate text segments for clients not meeting the desired
- document to different clients. Here is a simple example of how this can
- client and if "image/jpeg" is among them then use the
- Cookie header, the client hostname, or the client IP
- would display the "Here is some text ..." to those clients
- the client.
- "Restricted Local Stuff" only to clients on hosts
- number of separate files. This can make it very difficult for a client
- wrapper, or the search item provided by the client into a searchwrapper
- Title: Filters on the WN server
Matching lines:
- utility which uncompresses it. Then the client is served the
- fly and served to the client as a text/plain document.
- data provided by the client on its UNIX
- Title: Ranges on the WN server
Matching lines:
- the file. This is normally done automatically by the client in
- Title: Limiting Access to Your WN Hierarchy
Matching lines:
- This will limit access to the server to those clients with an IP address
- end with a period. If a subnet address is listed any client with an IP
- the IP address of the remote client, do a logical "and" of each of its
- line is to notify the client that for any document on this server with
- be valid, so the client need not ask the user for a username and
- that no publicly available clients currently support it. It is
- experimental, because I have no client to test it and hence it has barely
- Title: Users' Hierarchies and Personal Home Pages on the WN server
Matching lines:
- Then when a client sends a request like
- the server will return a redirect to the client for
- Title: Multi-homed or Virtual Servers on the WN server
Matching lines:
- client.com 111.222.222.111 /usr/wn/client client george clientgroup 1
- Title: WN Auxiliary Modules
Matching lines:
- Authentication scheme supported by most clients and future releases will
- is a designation which is sent to the client with the authorization
- request allowing the client to decide whether the user has already
- Title: Clickable Images and Imagemap files on the WN Server
Matching lines:
- URL to which the client should be directed after clicking in one of these
- If your imagemap file redirects the client to other documents on your
- HTTP/1.1 redirect to the client
- causing the client to automatically access this URL.
- redirect is sent because simply sending the file would confuse the client
- redirect to the client. This is necessary for the client to be able to
- or a document to the client but instead sending a header with status 204.
- This instructs the client to do nothing and in particular not to reload
- Title: Using CGI Programs on the WN Server
Matching lines:
- entirely different documents based on the the client request, the
- client's hostname, IP address, user-agent, or the "referer", the document
- # From now on everything goes to the client
- attempts to dissuade clients and proxies from caching the output by
- it prints out the client's hostname, user agent and the URL of the
- gets this information about the client from environmental variables set
- Title: Configuration File for the WN Package
Matching lines:
- * clients.
- * request. Some clients have buggy implementations of this so
- * Uncomment this if you want to try to check that the client is not
- * (aka RFC1413, IDENT, or TAP) lookups on clients. This may be good for
- * request from that client, so pages with lots of inline images will
- * Doing this means that if more than one client is using your server
- Title: Command Line Options for the WN Server
Matching lines:
- the client headers plus some additional information in the log file.
- clients actually send.
- a DNS lookup on the client's IP address to obtain the
- hostname of the client for logging purposes. If the
- Title: Index File Directives for the WN Server
Matching lines:
- error message is returned to the client. It is also possible to
- authentication, where "user" is the client supplied user
- name and "password" the client supplied password. The
- a DNS lookup on the client's IP address to obtain the
- hostname of the client for logging purposes. If the
- any "If-Modified-Since" date sent by the client and
- from the client to use a persistent connection.
- to encourage clients and proxies not to cache this document. It
- to the object is made by a client an error will be returned.
- been set by the client. It should never be located
- stream of that program to be sent to the client instead of the file
- to the client. Another example would be
- The client will then automatically request the new URL. The file
- a status 204 "no response" which tells the client to do
- header for use with "client-pull".
- client receiving this header supports "client-pull" (currently only
- client receiving this header supports cookie caching (currently only
- Normally the client will discard the cookie at the end of a session.
- and the combined document is sent to the client. It is possible to
- Title: Parsed Document Syntax for the WN Server
Matching lines:
- client's Accept headers
- the Accept headers supplied by the client. Or for the
- client's Accept-Charset headers
- the Accept-Charset headers supplied by the client. Or for the
- client's Accept-Encoding headers
- the Accept-Encoding headers supplied by the client. Or for the
- -- Match client's Accept-Language headers
- the Accept-Language headers supplied by the client. Or
- Match client's Cookie headers
- the Cookie headers supplied by the client.
- Match client's environment variable VAR
- -- Match client's hostname
- hostname of the client (in the first case) or if the file
- -- Match server's virtual hostname from client's HTTP Host header
- client in its request.
- client's IP address
- address of the client (in the first case) or if the file
- -- Match client's Accept-Language headers
- the Accept-Language headers supplied by the client. Or
- query string supplied by the client in the URL (in the first case) or
- Maximum number of matches per file exceeded.
- Title: CGI and other Environment Variables for the WN Server
Matching lines:
- Contains the length of information provided by a client
- Contains the content type supplied by the client with
- by the client.
- supplied by the client.
- supplied by the client.
- by the client.
- the client. This may contain the e-mail address of the client user.
- the real e-mail address of the client user.
- the client. This should contain the one of the aliases for the host
- URL that the client is requesting. Thus a client seeking
- by the client.
- by the client. This is supposed to contain the URL of the document
- supplied by the client. This is supposed to contain the name of the
- browser which the client is using to make this request
- Contains the IP address of the client or proxy making the request.
- Contains the hostname of the client or proxy making the request, if
- server on the client (if there is one and you have compiled the
- "PUT", depending on the method of the client request.
- protected this will contain the user name provided by the client.
- HTTP_HOST if the client
- Maximum number of matches per file exceeded.
- Title: Configuration Macros for WN
Matching lines:
- lookups on clients using the UNIX
- request from that client, so pages with lots of in-line images will
- Title: Changelog for WN
Matching lines:
- Modified server so that data reflected to client in
- the clients query data returned by <!-- #query -->.
- made multipart/byteranges fail. Either the client or the plugin
- which indicates the port the remote client or proxy is using.
- instead of 1.1 even if the client is 1.1.
- of client errors in range requests.
- "Cache-control: no-cache" headers attempting to encourage clients and
- the remote client disonnected in mid transaction.
- take the IP address of the remote client, do a logical "and" of each
- dynamic by default to discourage clients and proxies from caching
- Host: header (if any) supplied by the client. It should contain the name
- of the alias for *your* host which the client got from the URL. When all
- clients provide this virtual servers will be possible without multiple
- Added -d command line option which causes all headers etc. from client
- Added wn_pipeclosed() function to wn.c to log something when client
- other conditional parsed text but matches against clients request.
- posted by the client. The file is removed after the CGI script exits.
- client to do nothing and leave the display alone. This means in imagemaps
- with the link being invisible unless the client has access to the
- TAP) lookups on clients. This may be good for additional logging
- Maximum number of matches per file exceeded.
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]