summaryrefslogtreecommitdiff
path: root/NEWS
diff options
context:
space:
mode:
authorRobert James Kaes <rjkaes@users.sourceforge.net>2001-08-27 03:52:05 +0000
committerRobert James Kaes <rjkaes@users.sourceforge.net>2001-08-27 03:52:05 +0000
commitf72ebfe0d8de0feb3d31f8eb622c8959c4ea0253 (patch)
tree63654a5229f6718bbe9d896927d5c95e37056071 /NEWS
parentc25c7a947fb55d080da9bfdefdf1188e87b949a9 (diff)
downloadtinyproxy-f72ebfe0d8de0feb3d31f8eb622c8959c4ea0253.tar.gz
tinyproxy-f72ebfe0d8de0feb3d31f8eb622c8959c4ea0253.zip
More information regarding the various changes.
Diffstat (limited to '')
-rw-r--r--NEWS22
1 files changed, 12 insertions, 10 deletions
diff --git a/NEWS b/NEWS
index d6f9561..e95c271 100644
--- a/NEWS
+++ b/NEWS
@@ -3,21 +3,23 @@
====
Well so much for the 1.4.0 version being the best tinyproxy---there
-were bugs. The most serious was that anonymous filtering was not
-actually working. Another bug fix is that on Debian systems (and
-maybe others) child threads would not be closed if they had been
-created after tinyproxy had been started. Finally, if
-MaxClientRequests was set to 0, the status of the thread was not going
-back to T_WAITING.
+were bugs. The most serious was a segmentation fault problem when an
+invalid request was received. Also, anonymous filtering was not
+actually working. Another bug fix is that on Debian systems (and maybe
+others) child threads would not be closed if they had been created
+after tinyproxy had been started. Finally, if MaxClientRequests was
+set to 0, the status of the thread was not going back to T_WAITING.
-Okay, now on to the new features. There is only one feature which is
-the new Connect log level. This is basically "Info" without info's
-noise.
+Okay, now on to the new features. There is a new Connect log
+level. This is basically "Info" without info's noise. Also, the error
+reporting function sends back more HTTP headers, which should lead to
+a more standards compliant proxy.
There are a couple of features which I'm working on for the next
release. There has been requests for logging on tunnelled
connections. Also, some people would like HTTP filtering on tunnelled
-connections.
+connections. Finally, I do have the information to include SSL
+connections, so I will be including it in the next release.
So, the above bugs are fixed, hopefully there are no other ones. The
new features will be worked into the next few releases. \ No newline at end of file