You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by Chuck Murcko <ch...@hyperreal.com> on 1997/02/20 05:26:09 UTC

cvs commit: apache/htdocs/manual/mod mod_proxy.html

chuck       97/02/19 20:26:08

  Modified:    htdocs/manual/mod  mod_proxy.html
  Log:
  Fix typo; add section about SOCKS 4.2/Solaris problems.
  
  Revision  Changes    Path
  1.13      +4 -1      apache/htdocs/manual/mod/mod_proxy.html
  
  Index: mod_proxy.html
  ===================================================================
  RCS file: /export/home/cvs/apache/htdocs/manual/mod/mod_proxy.html,v
  retrieving revision 1.12
  retrieving revision 1.13
  diff -C3 -r1.12 -r1.13
  *** mod_proxy.html	1997/01/09 07:29:12	1.12
  --- mod_proxy.html	1997/02/20 04:26:07	1.13
  ***************
  *** 312,320 ****
    Yes. Just build Apache with the rule <code>SOCKS4=yes</code> in your
    <i>Configuration</i> file, and follow the instructions there. SOCKS5 
    capability can be added in a similar way (there's no <code>SOCKS5</code>
  ! rule yet, so use the <code>EXTRA_LFLAGS</code> definition, or build Apache
    normally and run it with the <i>runsocks</i> wrapper provided with SOCKS5,
    if your OS supports dynamically linked libraries.<p>
    
    Remember that you'll also have to grant access to your Apache proxy machine by
    permitting connections on the appropriate ports in your SOCKS daemon's
  --- 312,323 ----
    Yes. Just build Apache with the rule <code>SOCKS4=yes</code> in your
    <i>Configuration</i> file, and follow the instructions there. SOCKS5 
    capability can be added in a similar way (there's no <code>SOCKS5</code>
  ! rule yet), so use the <code>EXTRA_LFLAGS</code> definition, or build Apache
    normally and run it with the <i>runsocks</i> wrapper provided with SOCKS5,
    if your OS supports dynamically linked libraries.<p>
  + 
  + Some users have reported problems when using SOCKS version 4.2 on Solaris.
  + The problem was solved by upgrading to SOCKS 4.3.<p>
    
    Remember that you'll also have to grant access to your Apache proxy machine by
    permitting connections on the appropriate ports in your SOCKS daemon's