[Table of Contents]
WN Documentation Search Results -- Matches
You may select a new search term and repeat your search:
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
- WN works. When the server receives a request, say for
- Title: Installation and Setup of WN
- socket on a privileged port and listen for requests. But immediately
- a request is made for a directory any the trailing '/' is
- GET requests described above.
- messages with your request.
- Title: Creating your WN data directory
- When someone sends a request to your server with only the server name and
- request is made for a directory, say with the URL
- http://host/dir1/dir2/, this will be translated to a request
- There are three situations when the client request will be denied but for
- which you can supply customized error messages. These are requests for
- non-existent files, requests for files which require a password but for
- which no valid password was given, and requests from an invalid host for
- file is requested and when a document protected by an
- access control file is requested from an
- protected file is requested without a password or with an invalid
- Title: Security on the WN Server
- requests are granted. Permission to serve a document must be explicitly
- if the request is of type GET, the arguments are examined to
- program. Thus if the request is of type POST, information
- Finally if the GET request has arguments but no
- '=' it is assumed to be an ISINDEX type request
- POST request). Furthermore only
- result in a request for a document outside the server data hierarchy the
- request is treated like a request containing illegal path characters. In
- POST request with post data in excess of 10 megabytes. This
- does not defend against multiple requests with large POST
- Title: Setting Up Searches on the WN Server
- You can customize the message offered requesting a search term by
- If a recursive title, keyword or fielded search is requested and some
- "keyword". The URL requested will end with
- Title: Parsed Text and Server Side Includes on the WN server
- second file, i.e. inserting the requested file inside the second at a
- HTML document then any request from
- Title: Filters on the WN server
- containing this data. The name of this file changes with each request,
- Title: Ranges on the WN server
- If the server receives a request like:
- filtered documents, the server will honor a byte range. A request for:
- A request for:
- requests the last 1024 bytes of the file.
- Requests for a specific range can also be made with the proposed
- "Range:". For example, if the server receives a request
- 200th. The header "Range: bytes=300-" requests all
- And "Range: bytes=-300" requests the last 300 bytes of
- Title: Limiting Access to Your WN Hierarchy
- keyword search is requested and some
- then requests from that site will be exempt from any password
- pair will be required for requests from these sites, even if they are
- at the beginning of the access file. When this is done and a request is
- requested to supply a user name and password.
- This specifies that any request for a document in this directory which is
- Title: Users' Hierarchies and Personal Home Pages on the WN server
- "http://hostname/~john/foo.html" to request a document in a
- equivalent of a URL request for "/foo.html" with a data root
- translated to a request for "/foo.html" with the data root
- translated to a request for "/foo.html" with root data
- Then when a client sends a request like
- Title: Multi-homed or Virtual Servers on the WN server
- single initial instance of the server which responds to all requests and
- name to which the request was sent. To use this method you need to edit
- Communicator) and so-called "full URL requests". For browsers that
- if a full URL request like
- received the request. The
- Title: WN Utility Programs
- request is served (the server won't bother to count the bytes in a line
- range request).
- requests for documents in one directory to requests for other URL's. If
- directory then every request for something in that directory will be
- redirected to a request for http://host/dir/foo.html.
- then a request for http://this_host/this_dir/whatever.html
- Title: WN Auxiliary Modules
- about the request. If you put the directive "
- same content-type as the requested document.
- function to have access to more information about the request. If you
- Authorization requests in WN are normally handled by an
- The contents the Authorization: request header is passed to
- request allowing the client to decide whether the user has already
- Title: Clickable Images and Imagemap files on the WN Server
- if any browser makes a request for the document and does not include the
- Title: Using CGI Programs on the WN Server
- entirely different documents based on the the client request, the
- served. This is because the server will alway interpret a request for
- in it, the request will fail.
- served in place of the document requested. This is a way to designate a
- http://host/foo.html is requested this will cause the
- Title: Default Index Cache Files
- pages must have a cache file in the directory of the requested
- Title: Configuration File for the WN Package
- /* WN supports the processing of multiple requests in a single TCP
- * request. Some clients have buggy implementations of this so
- * request from that client, so pages with lots of inline images will
- * returned to requests from remote hosts. WN is slightly more efficient
- Title: Format of index.cache file for WN
- Title: Command Line Options for the WN Server
- addition the server will reject any request with the HTML
- If this option is not used the server will reject any requests
- Title: Index File Directives for the WN Server
- Set URL for requests for which access is denied.
- specifies that any request for a document in this directory which is
- specifies that any request for a document in this directory which is
- -- Set substitute URL for requests for non-existent or unservable
- specifies that any request in this directory for a non-existent file
- request. This is may be useful if there is a "
- request without a ".cgi" suffix or a
- sequence of directories and a terminating file, i.e. a request
- fulfiling a request for this document and not honor a request
- its output to be served in place of the document requested.
- So when http://host/path2/foo.html is requested
- of use when redirecting requests for non-existent files to an error
- cause a request for foo to be answered with an
- The client will then automatically request the new URL. The file
- pairs and include them in the request headers when documents in the
- Title: Parsed Document Syntax for the WN Server
- client in its request.
- Match query string supplied in request URL
- #if request --
- Match client's request
- <!-- #if request =~ "regexp" -->
- <!-- #if request file = "foo" -->
- contents of the full text of the request supplied by the client (in
- regular expression (in the second case). The full request contains
- URL requested with the "http://host" part having been
- is included at the beginning of an HTML document then any request
- Title: CGI and other Environment Variables for the WN Server
- URL that the client is requesting. Thus a client seeking
- browser which the client is using to make this request
- request. This is whatever comes after the '?' in the
- variable. If the request was generated by an HTML "
- Contains the IP address of the client or proxy making the request.
- Contains the hostname of the client or proxy making the request, if
- "PUT", depending on the method of the client request.
- determined by the IP address to which the request was made and the
- Title: Configuration Macros for WN
- Any request for a document in a directory which is denied because of an
- This is the document returned in response to a request with only the
- Default file name if the requested URL does not include a file name.
- Specifies that any request in this directory for a non-existent file or a
- request from that client, so pages with lots of in-line images will
- Title: Changelog for WN
- Modified dedot in prequest.c to be more efficient and eliminate
- from some range requests (thanks to S. Trier).
- requests for files from that directory failed.
- wrappers to fail when there are multiple search requests in a
- Fixed bug that caused MD5 header to be sent on range requests.
- Added support for return status 413 "Request entity too large".
- is primarily of use when redirecting requests for non-existent
- number of bytes sent for responses to byterange requests.
- used when the requested file did not exist. It should also be used
- of client errors in range requests.
- search was requested with no search term (reported by Hans
- Fixed bug in wn/wn.c which caused a timeout with POST requests
- The server now checks that any file which is requested and is not
- WN's byterange requests specified in URLs like
- requests. Also added better error handling in wn/send.c sendrange()
- since is in the index file. So when http://host/foo.html is requested
- Fixed bugs in wn/prequest.c and wn/parse.c so that redirects
- Fixed bug in wn/prequest.c that caused virtual hosting to work
- Fixed bug in wn/prequest.c so virtual host name comparison is
- Fixed bug in chkcntrl.c which caused a segmentation fault if a request
- Maximum number of matches per file exceeded.
- Title: Quick start
- The -v verbose option requests verbose logging (you only need to use
- it if you didn't request verbose logging in answer to the configure script
- Title: GNU Free Documentation License
- It is requested, but not required, that you contact the authors of the
WN version 2.5.0
Copyright © 1998-2005 John Franks
licensed under the GNU Free Documentation License
Last modified: Sat June 18 2005
[Table of Contents]