Changes to reflect the various fixes to have CONNECT upstream proxying
work.
This commit is contained in:
parent
1bbf32f04c
commit
2da1378f53
10
ChangeLog
10
ChangeLog
@ -1,5 +1,15 @@
|
|||||||
2001-10-25 Robert James Kaes <rjkaes@flarenet.com>
|
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
|
* src/reqs.c (relay_connection): Empty the contents of both
|
||||||
buffers when either socket is closed. This is more in line with
|
buffers when either socket is closed. This is more in line with
|
||||||
what a tunnel should do. Since either end could close with
|
what a tunnel should do. Since either end could close with
|
||||||
|
Loading…
Reference in New Issue
Block a user