Introduction
------------

What is Squid?
- See www.squid-cache.org

What version of Squid is included in this package?

- Squid 2.6 Stable 9 with additional fixes for EMX compatibility and eComStation performance enhancements. 
  Main port tested to destruction (1000+ workstations). Built with support for 8192 filedescriptors.

What Squid features are built in this version?
- There are two builds supplied in the distribution:
  1. SQUID.EXE - Standard HTTP/SSL Proxying, ICP and ICMP RTT Pinging. UFS and NULL storage available plus LRU and HEAP policies.
  2. SQUID-SSL.EXE - As SQUID.EXE, but with additional Delay-Pools, HTCP and (Open)SSL support (this support allows Squid to be used as an SSL bridge
  when being used as a *reverse* proxy). This support is untested. OpenSSL support is not required for normal HTTP/HTTPS proxy usage.
  3. SQUID-XFOR.EXE - As SQUID.EXE, but with additional Delay-Pools, HTCP and experimental X-Forwarded-For support. This is experimental and untested.

Do I need SQUID-SSL.EXE for standard SSL proxying?
- No. Read the Squid documentation. Specific SSL build is only required if you require REVERSE proxy, e.g. you want to HTTPS/secure a website that would otherwise be HTTP.
  You need to use SQUID-SSL.EXE only if you require reverse SSL support, or delay pools.

What other tools for the SSL support are there?
- In the SSLTOOLS sub-directory are the OpenSSL tools. They are not required for normal Squid operation.
  To use the tools, you will need to copy the supplied GCC321M.DLL file into a directory in your LIBPATH, e.g. \OS2\DLL.

How do I use SQUID-SSL.EXE ?
- Backup SQUID.EXE, and then copy SQUID-SSL.EXE over SQUID.EXE. You will also need to configure your SQUID.CONF.
  ** NOTE THAT THE SSL AND DELAY POOLS FEATURES HAVE NOT BEEN EXTENSIVELY TESTED **
  ** A KNOWN SQUID BUG IS THAT DELAY POOLS STOP WORKING AFTER SQUID -K RECONFIGURE IS USED **

What version of OpenSSL was built into SQUID-SSL.EXE?
- OpenSSL, ported by me for eComStation, version 0.9.8d was used.

What can SQUID-XFOR.EXE be used for?
- This allows you to specify access control (ACLs) based on the real-IP of a client which is already using a proxy.
  Therefore, in a chain or hierarchy of proxies, you can still use ACLs by asking Squid to examine the forwarded-for headers.
  This support in the OS/2 port is experimental.

What other OS/2 specific port issues are fixed in the release?
- Full support for "-k rotate" and "-k reconfigure" plus redirector support.

What do I need to run Squid?
- HPFS/JFS, EMX 0.9d fix 4 and OS/2 TCP/IP Version 4.1+. 

Will these Squid builds run on Warp 3, or Warp 4 without TCP/IP 4.1?
- No. TCP/IP 4.1+ is required, as this build is performance enhanced by calling the TCP/IP stack directly for some calls, rather than EMX.

How do I get Squid up and running?
- Read the FAQ on the Squid website. 
  Don't forget to configure SQUID.CONF first, and make your swap directories using SQUID -z!

Where can I get support from?
- There is an official Squid mailing list.


OS/2 Specific Features
----------------------

Nameserver File
- This version of Squid correctly uses the RESOLV2 file in the MPTN\ETC directory

Squid Home Directory
- Squid defaults to being in the \SQUID directory. You can change this by setting an environment varible (or batch file) as follows:
		SET SQUID_DIRECTORY=c:\utils\squid


Credits
-------

My port is based in part on the work done on an earlier Squid port by Alex Leko. 
The first OS/2 port was by Peter Meerwald for version 1.1.0 and 1.1.15.

Please contact me if you need a build with different options made or require help with issues specific to the OS/2 port.

Steve Sharrad
England, UK 25th January 07
steve@stevesharrad.co.uk
