diff options
| author | Robert James Kaes <rjkaes@users.sourceforge.net> | 2001-10-25 05:13:18 +0000 |
|---|---|---|
| committer | Robert James Kaes <rjkaes@users.sourceforge.net> | 2001-10-25 05:13:18 +0000 |
| commit | 2da1378f53cc019c7bfb11fbd24267d69d05e8af (patch) | |
| tree | bdf4b59568cf12c47bd3a89c6da38d3e1184bdf4 | |
| parent | 1bbf32f04c08993a79200f33ed81f3a6f7123a7a (diff) | |
| download | tinyproxy-2da1378f53cc019c7bfb11fbd24267d69d05e8af.tar.gz tinyproxy-2da1378f53cc019c7bfb11fbd24267d69d05e8af.zip | |
Changes to reflect the various fixes to have CONNECT upstream proxying
work.
| -rw-r--r-- | ChangeLog | 10 |
1 files changed, 10 insertions, 0 deletions
@@ -1,5 +1,15 @@ 2001-10-25 Robert James Kaes <rjkaes@flarenet.com> + * src/reqs.c (process_client_headers): Selectively send headers + based on whether we're using an upstream with a CONNECT + request. The short answer: all methods work correctly with + Upstream proxying and normal proxying. + + * src/tinyproxy.h: Added a upstream flag to the conn_s structure + so we can figure out when to send headers and when not to send + headers. This is extremely important when trying to do upstream + proxying of the CONNECT method. + * src/reqs.c (relay_connection): Empty the contents of both buffers when either socket is closed. This is more in line with what a tunnel should do. Since either end could close with |