Note that there is currently work in progress to leverage curl's
test suite, patches have been submitted upstream:
https://curl.se/mail/lib-2014-06/0070.html
+ https://curl.se/mail/lib-2021-01/0068.html
3) Fix some more XXX: comments.
86) Add a server-body-tagger action. This is trivial as as all the
functionality required to do it already exists.
-87) Add a client-body-tagger action. This is less trivial as we currently
- don't buffer client bodies. After 14) is implemented it would be
- trivial, though.
+87) Add a client-body-tagger action. This, too, is trivial.
88) Investigate if there's a Perl module that Privoxy-Regression-Test
could optionally use to keep connections alive, preferably while
169) Preserve all relevant copyright and license statements in binary
packages we distribute.
-170) Serve the ca-cert-file through the CGI interface so client's
+170) Serve the ca-cert-file through the CGI interface so clients
can conveniently import it (insecurely).
171) Create a "view page using Privoxy" website where users can input
181) Allow to upgrade an http request to https behind the
client's back using a client-header filter.
+182) Before enforcing the client-header-order, check that the
+ client headers actually need sorting. Should reduce log
+ messages and memory allocations.
+
+183) Properly deal with proxy responses that arrive in multiple pieces
+ when https inspecting while using a forwarding proxy.
+
+184) Add support for wolfSSL. Work in progress, expected to be
+ committed after the 3.0.30 release.
+
+185) The mbedTLS and OpenSSL versions of generate_host_certificate()
+ should only be called when necessary and the check should be
+ done without holding the certificate mutex.
+
+186) Privoxy should handle "OPTIONS *" requests properly.
+
+187) There should be a convenient way to see the versions of
+ the libraries Privoxy is using.
+
+188) In the windows config.txt file, add the line
+ user-manual ./doc/user-manual/
+ right after
+ # Copyright ...
+ #
+
+189) Bring back binary packages for macOS, preferably for both Intel and M1.
+ The first step would be getting at least one build system, either
+ donated or bought with donations earmarked for this.
+ Interested donors: 0.
+
+190) The socks5 authentication code should send user name an password
+ seperately or we should increase the cbuf size to allow longer
+ user names and passwords.
+
+191) The cipher-list directive should be split into cipher-list-server
+ and cipher-list-client.
+
+192) The client TLS contexts should probably be shared among threads
+ to spend less time and memory loading the root certificates.
+
##########################################################################
Hosting wish list (relevant for #53)