Browse files

This commit was manufactured by cvs2svn to create tag


git-svn-id: 13f79535-47bb-0310-9956-ffa450edef68
  • Loading branch information...
No Author
No Author committed Feb 5, 2001
1 parent 3e1fefd commit 8ad65fb2cf5d519448e0ab670e5c3f76794a35ce
Showing with 0 additions and 10,642 deletions.
  1. +0 −78 docs/manual/bind.html.en
  2. +0 −93 docs/manual/cgi_path.html.en
  3. +0 −248 docs/manual/configuring.html.en
  4. +0 −590 docs/manual/content-negotiation.html.en
  5. +0 −177 docs/manual/custom-error.html.en
  6. +0 −1,161 docs/manual/developer/API.html
  7. +0 −203 docs/manual/developer/modules.html.en
  8. +0 −394 docs/manual/dso.html.en
  9. +0 −156 docs/manual/handler.html.en
  10. +0 −519 docs/manual/howto/ssi.html.en
  11. +0 −174 docs/manual/index.html.en
  12. +0 −199 docs/manual/install.html.en
  13. +0 −118 docs/manual/invoking.html.en
  14. +0 −283 docs/manual/mod/directive-dict.html.en
  15. +0 −144 docs/manual/mod/module-dict.html.en
  16. +0 −90 docs/manual/mpm.html.en
  17. +0 −94 docs/manual/new_features_2_0.html.en
  18. +0 −170 docs/manual/sections.html.en
  19. +0 −113 docs/manual/server-wide.html.en
  20. +0 −192 docs/manual/stopping.html.en
  21. +0 −516 docs/manual/suexec.html.en
  22. +0 −143 docs/manual/upgrading.html.en
  23. +0 −59 docs/manual/vhosts/fd-limits.html.en
  24. +0 −65 docs/manual/vhosts/index.html.en
  25. +0 −169 docs/manual/vhosts/name-based.html.en
  26. +0 −1,296 modules/arch/win32/mod_isapi.c
  27. +0 −86 modules/test/mod_optional_fn_export.c
  28. +0 −3 modules/test/mod_optional_fn_export.h
  29. +0 −93 modules/test/mod_optional_fn_import.c
  30. +0 −5 server/mpm/experimental/perchild/.cvsignore
  31. +0 −5 server/mpm/experimental/perchild/
  32. +0 −88 server/mpm/experimental/perchild/mpm.h
  33. +0 −144 server/mpm/experimental/perchild/mpm_default.h
  34. +0 −1,832 server/mpm/experimental/perchild/perchild.c
  35. +0 −738 server/mpm/winnt/Win9xConHook.c
  36. +0 −10 server/mpm/winnt/Win9xConHook.def
  37. +0 −103 server/mpm/winnt/Win9xConHook.dsp
  38. +0 −91 server/mpm/winnt/Win9xConHook.h
@@ -1,78 +0,0 @@
-<TITLE>Setting which addresses and ports Apache uses</TITLE>
-<!-- Background white, links blue (unvisited), navy (visited), red (active) -->
- TEXT="#000000"
- LINK="#0000FF"
- VLINK="#000080"
- ALINK="#FF0000"
-<!--#include virtual="header.html" -->
-<H1 ALIGN="CENTER">Setting which addresses and ports Apache uses</H1>
-<p>When Apache starts, it connects to some port and address on the
-local machine and waits for incoming requests. By default, it
-listens to all addresses on the machine, and to the port
-as specified by the <code>Port</code> directive in the server configuration.
-However, it can be told to listen to more the one port, or to listen
-to only selected addresses, or a combination. This is often combined
-with the Virtual Host feature which determines how Apache
-responds to different IP addresses, hostnames and ports.</p>
-<p>The <code>Listen</code> directive tells the server to accept
-incoming requests only on the specified port or address-and-port
-combinations. If only a port number is specified in the
-<code>Listen</code> directive, the server listens to the given port on
-all interfaces, instead of the port given by the <code>Port</code>
-directive. If an IP address is given as well as a port, the server
-will listen on the given port and interface. Multiple Listen
-directives may be used to specify a number of addresses and ports to
-listen to. The server will respond to requests from any of the listed
-addresses and ports.</P>
-<p>For example, to make the server accept connections on both port
-80 and port 8000, use:
- Listen 80
- Listen 8000
-To make the server accept connections on two specified
-interfaces and port numbers, use
- Listen
- Listen
-<H2>How this works with Virtual Hosts</H2>
-<p>Listen does not implement Virtual Hosts. It only tells the
-main server what addresses and ports to listen to. If no
-&lt;VirtualHost&gt; directives are used, the server will behave the
-same for all accepted requests. However, &lt;VirtualHost&gt; can be
-used to specify a different behavior for one or more of the addresses
-and ports. To implement a VirtualHost, the server must first be told
-to listen to the address and port to be used. Then a
-&lt;VirtualHost&gt; section should be created for a specified address
-and port to set the behavior of this virtual host. Note that if the
-&lt;VirtualHost&gt; is set for an address and port that the server is
-not listening to, it cannot be accessed.
-<H2>See also</H2>
-See also the documentation on
-<a href="mod/mpm_common.html#listen">Listen directive</a>,
-<A HREF="vhosts/">Virtual Hosts</A>,
-<A HREF="mod/core.html#port">Port directive</A>,
-<A HREF="dns-caveats.html">DNS Issues</A>
-<A HREF="mod/core.html#virtualhost">&lt;VirtualHost&gt; section</A>.
-<!--#include virtual="footer.html" -->
@@ -1,93 +0,0 @@
-<TITLE>PATH_INFO Changes in the CGI Environment</TITLE>
-<!-- Background white, links blue (unvisited), navy (visited), red (active) -->
- TEXT="#000000"
- LINK="#0000FF"
- VLINK="#000080"
- ALINK="#FF0000"
-<!--#include virtual="header.html" -->
-<H1 ALIGN="CENTER">PATH_INFO Changes in the CGI Environment</H1>
-<H2><A NAME="over">Overview</A></H2>
-<P>As implemented in Apache 1.1.1 and earlier versions, the method
-Apache used to create PATH_INFO in the CGI environment was
-counterintuitive, and could result in crashes in certain cases. In
-Apache 1.2 and beyond, this behavior has changed. Although this
-results in some compatibility problems with certain legacy CGI
-applications, the Apache 1.2 behavior is still compatible with the
-CGI/1.1 specification, and CGI scripts can be easily modified (<A
-HREF="#compat">see below</A>).
-<H2><A NAME="prob">The Problem</A></H2>
-<P>Apache 1.1.1 and earlier implemented the PATH_INFO and SCRIPT_NAME
-environment variables by looking at the filename, not the URL. While
-this resulted in the correct values in many cases, when the filesystem
-path was overloaded to contain path information, it could result in
-errant behavior. For example, if the following appeared in a config
- Alias /cgi-ralph /usr/local/httpd/cgi-bin/user.cgi/ralph
-<P>In this case, <CODE>user.cgi</CODE> is the CGI script, the "/ralph"
-is information to be passed onto the CGI. If this configuration was in
-place, and a request came for "<CODE>/cgi-ralph/script/</CODE>", the
-code would set PATH_INFO to "<CODE>/ralph/script</CODE>", and
-SCRIPT_NAME to "<CODE>/cgi-</CODE>". Obviously, the latter is
-incorrect. In certain cases, this could even cause the server to
-<H2><A NAME="solution">The Solution</A></H2>
-<P>Apache 1.2 and later now determine SCRIPT_NAME and PATH_INFO by
-looking directly at the URL, and determining how much of the URL is
-client-modifiable, and setting PATH_INFO to it. To use the above
-example, PATH_INFO would be set to "<CODE>/script</CODE>", and
-SCRIPT_NAME to "<CODE>/cgi-ralph</CODE>". This makes sense and results
-in no server behavior problems. It also permits the script to be
-guaranteed that
-will always be an accessible URL that points to the current script,
-something which was not necessarily true with previous versions of
-<P>However, the "<CODE>/ralph</CODE>"
-information from the <CODE>Alias</CODE> directive is lost. This is
-unfortunate, but we feel that using the filesystem to pass along this
-sort of information is not a recommended method, and a script making
-use of it "deserves" not to work. Apache 1.2b3 and later, however, do
-provide <A HREF="#compat">a workaround.</A>
-<H2><A NAME="compat">Compatibility with Previous Servers</A></H2>
-<P>It may be necessary for a script that was designed for earlier
-versions of Apache or other servers to need the information that the
-old PATH_INFO variable provided. For this purpose, Apache 1.2 (1.2b3
-and later) sets an additional variable, FILEPATH_INFO. This
-environment variable contains the value that PATH_INFO would have had
-with Apache 1.1.1.</P>
-<P>A script that wishes to work with both Apache 1.2 and earlier
-versions can simply test for the existence of FILEPATH_INFO, and use
-it if available. Otherwise, it can use PATH_INFO. For example, in
-Perl, one might use:
- $path_info = $ENV{'FILEPATH_INFO'} || $ENV{'PATH_INFO'};
-<P>By doing this, a script can work with all servers supporting the
-CGI/1.1 specification, including all versions of Apache.</P>
-<!--#include virtual="footer.html" -->
Oops, something went wrong.

0 comments on commit 8ad65fb

Please sign in to comment.