diff options
author | Robert James Kaes <rjkaes@users.sourceforge.net> | 2001-05-30 16:11:13 +0000 |
---|---|---|
committer | Robert James Kaes <rjkaes@users.sourceforge.net> | 2001-05-30 16:11:13 +0000 |
commit | 0b98f16c616764a690b9f5fbc7359e72a72b873e (patch) | |
tree | e3dcf19aa4fe3575d1e1f8ef9a0e4ba34faa9053 | |
parent | 86bbc9764f549addd615e6233b6e8c78402ac43b (diff) | |
download | tinyproxy-0b98f16c616764a690b9f5fbc7359e72a72b873e.tar.gz tinyproxy-0b98f16c616764a690b9f5fbc7359e72a72b873e.zip |
Added a few points for future work on tinyproxy.
-rw-r--r-- | doc/TODO | 10 |
1 files changed, 7 insertions, 3 deletions
@@ -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 examples of how it's done right now). - 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 - the URL and rewrite it. If we want to go really fancy with RegEx - mapping this could get ugly. :) + much of a problem. Just need to modify the process_method() code + to look up the URL and rewrite it. If we want to go really fancy + with RegEx mapping this could get ugly. :) - Ed Avis suggests having tinyproxy have the ability to send the data 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. + - 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.
\ No newline at end of file |