[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: Which proxy to use?
- To: or-talk@xxxxxxxxxxxxx
- Subject: Re: Which proxy to use?
- From: "Mr. Blue" <trashdsfg@xxxxxxxxx>
- Date: Fri, 7 Aug 2009 05:21:58 -0700 (PDT)
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: or-talk-outgoing@xxxxxxxx
- Delivered-to: or-talk@xxxxxxxx
- Delivery-date: Fri, 07 Aug 2009 08:22:04 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1249647718; bh=knf1I7QwAQ6mzBgDz9WEco4Ty/wUOeTtBjvo2cEC9/c=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=hx4wCkj2x+LwyRH2xnX+lqMdi/gTtLwTnUR3mbKPdGGVn2PLVMEL97t9EAbceZnrxWAS14iIdUTiPKUkaUCdjv7PSV2vNBfQHqSDeZRR2faeL9Eg1k3L/UdeaY9ZB7+kVUQ5Dz+8J07C8xJ74ljWKmYk4RKnSfnTxPpgyyQ4gfM=
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=VTpldYXVCduM55M1i1g10Ykf3ZjpoNu4lDsDeRIvOxls/6MW7Y8t00HPSP/5RkWxWpYHdvMljMC/PabWYIxBvWcL7fk9eYB31ZNa25gGmDQuS51SGEbcYAq1cU8IUXUve+HHyqHglOppGpMOQM0WNuVsq8+PY2v+bKPO18E2QAQ=;
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
----- Original Message -----
From: Fabian Keil <freebsd-listen@xxxxxxxxxxxxx>
To: or-talk@xxxxxxxxxxxxx
Date: Tue, 4 Aug 2009 21:13:06 +0200
Subject: Re: Which proxy to use?
> > > On Sat, Aug 1, 2009 at 9:19 AM, Mr. Blue<trashdsfg@xxxxxxxxx> wrote:
>
> > > > 2) Must be capable to run as a reverse proxy.
>
> > > what are you trying to do, exactly?
>
> > I wana have ONE proxy app installed
> > Well, curently, I am using privoxy, which achieves
> > a) exit notattion striping, but it can not act as a b) reverse proxy.
>
> What's your definition of "reverse proxy"?
>
> If you simply want the proxy to process intercepted requests,
> you may want to have a look at Privoxy's accept-intercepted-requests
> directive.
>
> Fabian
>
Eh, smart counter question.
Basically, proxy(which acts as a reverse) and firewall are on one IP/machine(A) to which shall be send http or any other requests by clients.
All others services are on other IPs, like web on one IP and database on second IP/machine etc...
Clients always see IP of machine (A).
For example request to (A) for http, makes (A) forward that request to machine (B), which has a http server installed and sends it back to (A), which then serves it back to the client.
All headers, notations, IP...etc, must be exactly same as (A) served that request directly to the client.
Basically, each service has it's own machine and IP, but are all accessed through (A) and are served like (A) directly served them.