httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From n.@apache.org
Subject cvs commit: httpd-2.0/docs/manual/mod mod_proxy.html.en
Date Sun, 06 Jul 2003 02:25:21 GMT
nd          2003/07/05 19:25:21

  Modified:    docs/manual/mod mod_proxy.html.en
  Log:
  update transformation
  
  Revision  Changes    Path
  1.32      +8 -9      httpd-2.0/docs/manual/mod/mod_proxy.html.en
  
  Index: mod_proxy.html.en
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_proxy.html.en,v
  retrieving revision 1.31
  retrieving revision 1.32
  diff -u -r1.31 -r1.32
  --- mod_proxy.html.en	29 May 2003 16:13:24 -0000	1.31
  +++ mod_proxy.html.en	6 Jul 2003 02:25:21 -0000	1.32
  @@ -45,21 +45,20 @@
       major overhaul for Apache v2.0. The protocol support was upgraded to
       <code>HTTP/1.1</code>, and filter support was enabled.</p>
   
  -    <p>During the overhaul process the <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code>
has been
  -    splitted into several module files. The accompanying modules distributed
  -    with the httpd are <code class="module"><a href="../mod/mod_proxy_http.html">mod_proxy_http</a></code>,
  +    <p>During the overhaul process, <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code>
features
  +    have been split into several module files: <code class="module"><a href="../mod/mod_proxy_http.html">mod_proxy_http</a></code>,
       <code class="module"><a href="../mod/mod_proxy_ftp.html">mod_proxy_ftp</a></code>
and <code class="module"><a href="../mod/mod_proxy_connect.html">mod_proxy_connect</a></code>.
  -    Thus if you want to use one or more of the particular proxy functions you
  -    have to load <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code>
<em>and</em> the appropriate
  +    Thus, if you want to use one or more of the particular proxy functions,
  +    load <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code>
<em>and</em> the appropriate
       module(s) into the server (either statically or dynamically via the
       <code class="directive"><a href="../mod/mod_so.html#loadmodule">LoadModule</a></code>
directive).</p>
   
       <p>Please note that the <strong>caching</strong> function present
in <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code>
up to Apache v1.3.x has been <strong>removed</strong>
  -    from <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code>
and will be incorporated into a new module,
  -    <code class="module"><a href="../mod/mod_cache.html">mod_cache</a></code>.
In other words: the Apache 2.0.x-Proxy doesn't 
  -    cache at all - all caching functionality has been moved into
  +    from <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code>
and incorporated into a new module,
  +    <code class="module"><a href="../mod/mod_cache.html">mod_cache</a></code>.
In other words, the Apache 2.0.x proxy doesn't 
  +    cache - all caching functionality has been moved into
       <code class="module"><a href="../mod/mod_cache.html">mod_cache</a></code>,
which is capable of caching any content, not
  -    only content from proxy.</p>
  +    just content from the proxy.</p>
   
       <p>If you need to use SSL when contacting remote servers, have a look at the
       <code>SSLProxy*</code> directives in <code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code>.</p>
  
  
  

Mime
View raw message