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

New news for the 1.5.0 release.

Browse Source
This commit is contained in:
Robert James Kaes 2002-04-09 01:45:07 +00:00
parent 6f06485dbd
commit 64e28312dc
1 changed files with 16 additions and 29 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

45
NEWS
View File

@ -2,34 +2,21 @@
NEWS NEWS
==== ====
There are a few problems with this version of tinyproxy, but I'm hoping It's been a few months since I release the 1.4.3 version. That's
the benefits outweigh the negative. For some reason tinyproxy is not a bit longer than I want to take with this release (which I originally
able to handle requests to *.x10.com sites. (As someone mentioned: "maybe thought would be released a week after the 1.4.3 release in November
this is a feature?" :) There also seem to be a few other random sites 21, 2001 :), but my real life kind of intruded on the project.
where tinyproxy is not communicating with the server correctly. If you Anyway, this release doesn't add any new features or functions; it's
find any such sites, let me know so I can add it to the list of domains basically a bug fix and standard compliance release. A few
where tinyproxy is failing. I'll need this information for the regression portability bugs have been fixed, and I've rewritten a few request
tests I plan on performing on the next release. processing functions to make them more compliant with the HTTP
standard.
As for the next release (1.5.0), I will not be adding new features. Now, I've tested the request related code personally with all the
tinyproxy doesn't currently conform correctly to either the HTTP/1.0 configurations I can think of, but I can't claim that it will work
or the HTTP/1.1 standards. The goal of the 1.5 release therefore is perfectly with _every_ configuration and _every_ site. So, please
to achieve standards compliance with at least HTTP/1.0. If you have give these pre-releases a thorough testing and let me know if there
looked at the tinyproxy code you will have noticed that all the real any problems you've noticed.
work of the proxy is performed in the reqs.c file. Therefore, other
than bug fixes in the other files, only reqs.c should be changed in
the 1.5.0 release. Basically, I'm hoping to just gut and replace the
reqs.c file with a standards compliant version and release a new version.
Depending on my schedule I should have the new version ready for Robert James Kaes
pre-testing sometime next week. If you have any suggestions for improving April 8, 2002
tinyproxy please let me know, but I will not be incorporating them until
1.6 (which _hopefully_ should come out fairly quickly after 1.5 has
stabilised.)
"Thank you" go out to all who have helped find bugs in the 1.4.3
candidates. You know who you are, and if you don't look in the ChangeLog
for your name. :)
Robert James Kaes
November 21, 2001