bughz/tinyproxy
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Updated to reflect the 1.4.0 release.

Browse Source
This commit is contained in:
Robert James Kaes 2001-05-30 16:02:41 +00:00
parent b5584c243a
commit abbdec5ca9
1 changed files with 19 additions and 34 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

53
NEWS
View File

@ -2,40 +2,25 @@
NEWS NEWS
==== ====
This is another interim release of tinyproxy that fixes a few more bugs, This is the long awaited 1.4.0 release of tinyproxy. Most of the
and adds a feature or two (notably: non-blocking DNS lookups). It was tinyproxy source has been rewritten in one form or another. The old
decided to move back what was previously going to be released as 1.3.2 and ADNS code has been removed, and the giant (ugly) state machine has
release it as 1.4.0, as these bug fixes and patches were determined to be been banished. These have been replaced by a threaded connection
too high-priority to wait on. system. Not only did this make the source code cleaner, but it should
improve performance on SMP machines.
In this version of 1.3.2, the are the following new features: Another change to tinyproxy is the new configuration file. Take a look
at doc/tinyproxy.conf for an example of how to configure tinyproxy. If
- Non-blocking DNS lookups. you have any experience configuring the Apache web server you will
immediately see similarities between the tinyproxy and Apache
And the following bug fixes: configuration files. In other words, we liberally copied from the
Apache style.
- A bug where connptr was not correctly being set before httperr was being
called in reqs.c.
- A bug where the system would crash if an empty request was received.
- A file descriptor leak where an fd would not be properly closed in
event of a bad HTTP request.
Here is some information on the upcoming 1.4.0 release: The access control list (ACL) feature of tinyproxy has been greatly
expanded. tinyproxy now allows you to selectively allow or deny a much
more specific set of IP addresses or subnets. In the same vein,
tinyproxy can be configured to only bind to one address on a
multi-homed machine.
1.4.0 If this version is not the best tinyproxy released, than it's pretty
===== darn close.
1.4.0 is in the works. Some features you can expect:
- Ability to listen on >1 port.
- Ability to set up more than one access list for the allowed
IP subnets.
- Ability to listen on multiple interfaces specified on the command-line.
- Simple caching.
Under the hood, 1.4.0 should be a bit more modular than 1.3.2. This
will hopefully lend itself towards making it easier for third parties to
develop new features for tinyproxy.
Please note that as of 1.3.1, Steven Young <sdyoung@well.com> is once
again the primary maintainer of tinyproxy.