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

Added a few points for future work on tinyproxy.

Browse Source
This commit is contained in:
Robert James Kaes 2001-05-30 16:11:13 +00:00
parent 86bbc9764f
commit 0b98f16c61
1 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/TODO
View File

@ -12,9 +12,13 @@ against the current tree and I'll integrate it if possible.
source than the current method. (see httperr() and showstats() for source than the current method. (see httperr() and showstats() for
examples of how it's done right now). examples of how it's done right now).
- Include a function to rewrite the incoming requests. Should not be - Include a function to rewrite the incoming requests. Should not be
much of a problem. Just need to modify the clientreq code to look up much of a problem. Just need to modify the process_method() code
the URL and rewrite it. If we want to go really fancy with RegEx to look up the URL and rewrite it. If we want to go really fancy
mapping this could get ugly. :) with RegEx mapping this could get ugly. :)
- Ed Avis suggests having tinyproxy have the ability to send the data - Ed Avis suggests having tinyproxy have the ability to send the data
from the connections through an external filtering program. I kind of from the connections through an external filtering program. I kind of
like this idea, but I don't really have a good way of doing it yet. like this idea, but I don't really have a good way of doing it yet.
- Handle Secure Socket Layer (SSL) connections (usually port 443).
- Allow selective logging. For example a person may only want to log
error messages.
- Include the ability to rewrite both incoming and outgoing headers.