- To: Linux Mailing List <slug@xxxxxxxxxxx>
- Subject: Re: [SLUG] setting up squid proxy
- From: Tony Sceats <tony.sceats@xxxxxxxxx>
- Date: Tue, 18 Aug 2009 18:57:24 +1000
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=1R5P6MtMy4Dvk7vQPEWaXO/W/vjMkEzyVRZiSSPeFSM=; b=SULpOfROTcgq9c+rt3Iijy2mLR2CsoWIkyh0743cqbd8v+Bb4w6EQlCqrxxZepALHy XTMmHrjoOkabVIlxg46MqmhTDSQByHpNFVowNlDQx2FPiNq+IK8tBA4Kpna0xXw57SdW zvnNaO/WuyTYA5RbtmwqhDRKdpAlqx8K/FQto=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=SOJvvTgGskgcOUFjmFP84rg3pX3jPdHceIZ66gXMVBhWQPuvXbzBYCySDgGTIfrUtB ZvSSyRdOgHvnWiyAIKz6orT/dBaDAyVMk7Y3IwYk3TbUX7BzW6ASz8VgnnkdMfGP2vbn zMnZ5FzH6hvcNA93M1YMkytl+5AB3kmmDBigA=
On Tue, Aug 18, 2009 at 6:47 PM, Robert Collins
<robertc@xxxxxxxxxxxxxxxxx>wrote:
> On Tue, 2009-08-18 at 18:38 +1000, Amos Shapira wrote:
> > 2009/8/18 Tony Sceats <tony.sceats@xxxxxxxxx>:
> > > what you're trying to do is usually referred to as a transparent
> reverse
> > > proxy.. you should be able to find heaps of info on this
> >
> > What's "transparent" about it? It's just "reverse proxy" as far as I
> know.
>
> Its not transparent at all - transparent involves handling
> non-proxy-ready http requests as well as TCP hijacking :)
but, um, don't you want you're "non-proxy-ready http requests" to get
through your reverse proxy and onto your internal web server as well?!
it would seem a bit silly otherwise, but that could just be me
And I wouldn't call this functionality anything close to TCP hijacking -
it's just TCP redirection, there's no hijacking any where in sight..
hijacking, as I would call it, is either taking over or inserting data into
an established TCP session, which is much more difficult than redirecting,
eg, outbound connections on port 80 to a local IP port 3128
SLUG Mailing List Archives