tor 2007-01-04 klockan 21:32 +0530 skrev L.Suresh: > - is it possible for squid to write the source ip/port of a http > request into the request header when it forwards to reverse proxy? I > need this information to make some network optimizations in reverse > proxy It already writes the source IP in the X-Forwarded-For header. > - squid reuses the connection with reverse proxy for a different > browser request. to be more clear, lets say browser B1 issued a http > request with keep-alive, squid forwards to reverse proxy (lets call > the link between squid and reverse proxy as link 1) and then it goes > downstream. Now if another browser B2 issues a request for the same > domain, squid reuses the link1 for this request. The problem is we > don’t parse http request boundaries in our reverseproxy module for > perf reasons and I would like link1 to be maintained only for browser > B1 and squid to open a new link to reverse proxy for B2. is this > possible? Only if you modify the code. The reasons why Squid does this is twofold: a) Recommended by the RFC b) Cuts down on the resource usage on the server as there is significantly less number of connections open, often several orders of magnitude difference. Assuming the connectivity is good Squid -> your_proxy -> origin you could just as well disable server side persistent connections I think. server_side_persistent off Regards Henrik
Attachment:
signature.asc
Description: Detta =?ISO-8859-1?Q?=E4r?= en digitalt signerad meddelandedel
