  INTRODUCTION
  ------------

"Low, the monster burst free despite the best efforts of the captives
to reign her in.  Slowly she flew over the countryside burning whole
sectors of the land.  As she winged off, the wise old wizard
exclaimed: 'The creature is loosed, but verily I say, she will return
stronger than before!'"

All right, so I'm over two weeks late with this release.  As some of
you know, I do contract programming as part of my business.  I've been
rather bogged down with a "needs to be done yesterday" project, so I
didn't have much time to look into tinyproxy.  In any case, this is
the final 1.6.0 release.  There have been a lot of changes since
1.5.3, so I would recommend that _everyone_ upgrade to this release.
You'll probably also want to look at the configuration file again to
find out how all the new directives work.

If you find any problems with tinyproxy, please post them to the
tinyproxy bug tracking system at Sourceforge:

	http://sourceforge.net/tracker/?group_id=2632

Discussions about problems with tinyproxy (or general usage
questions) can always be posted to the tinyproxy mailing list.  See
the end of this document for more information.


  CHANGES
  -------

Summary of changes since 1.6.0rc3:

 * Fixed a small bug in indicate_http_error().

Summary of changes since 1.6.0rc2:

 * Rewrote the new upstream code to better handle the various upstream
   configuration options.

 * Updated the scanner code to parse the configuration file correctly.

Summary of changes since 1.6.0rc1:

 * Made the report.sh script more portable.  It should now run without
   errors on most Posix compatible systems.

 * Added the INADDR_NONE define if it's not already defined.  This
   allows tinyproxy to compile on SunOS (Solaris 2.8).  Thank to Ben
   Hartshorne for the patch.

Summary of changes since 1.6.0pre4: No changes

Summary of changes since 1.6.0pre3:

 * Fixed the safefree() macro to make is safe as an rvalue and with
   code that may have side effects.

 * Added improved upstream proxy code from Peter da Silva.  Also
   included more examples on how to configure the directives correctly
   in the configuration file.

 * Fixed an off-by-one error in connect_to_upstream()

 * Removed the "ViaHeader" directive and replaced it with the
   "ViaProxyName" directive.  The HTTP "Via" header is required by the
   HTTP spec, so tinyproxy now includes it.  Use the "ViaProxyName"
   directive to make the server's host name.

Summary of changes since 1.6.0pre2:

 * Fixed a bug that would kill a child process.

 * Work around a bug in some HTTP daemons that do not like having the
   port number appended to the Host header if the connection is on a
   standard port.

 * Upstream proxy support is now configurable.  Different proxy
   servers can be configured to handle different requests.

Summary of changes since 1.6.0pre1:

 * Added work around code for a bug with Internet Explorers HTTP POST
   handling.

 * Fixed a bug with the transparent proxy code.  Filtering can now be
   done on the entire URL, rather than just the path portion.

 * A bit of code reorganization.  The conn structure will now track
   both client and server content-length fields.

Summary of changes since 1.5.3:

 * Added Steven Young's dynamic HTML error reporting facility.  This
   allows the HTML error messages to be stored as template files in
   the file system, rather than being hard-coded in the tinyproxy
   executable.

 * Implemented an HTTP message API to make an HTTP entity a concrete
   object.  I _believe_ this will be the first step toward added
   support for plug-in modules.

 * Included a bug fix to handle when connecting to servers not on the
   default port 80.

 * Made the tinyproxy statistics URL a configuration time option.

 * Improved the robustness of a few support functions.

 * Basic code clean up and reorganization.


 FUTURE
 ------

Here is a list of improvements slated for the next tinyproxy release:

 * Improve the shared memory implementation (maybe using the MM
   library.)


  CONCLUSION
  ----------

tinyproxy is shaping up to be a very useful little tool.  There are
still long term goals relating to making tinyproxy a completely
HTTP/1.1 standards compliant proxy.  Anyone with ideas or patches for
tinyproxy should submit them to the tinyproxy-users mailing list at:

	tinyproxy-users@lists.sourceforge.net

or see the project's page at:

	http://tinyproxy.sourceforge.net/
        http://sourceforge.net/projects/tinyproxy/

Thanks again to all those who have helped to make tinyproxy a more
useful utility.

	Robert James Kaes
	July 14, 2003
