On Thursday 14 January 2016 at 18:25:16, Robert Plamondon wrote:
> > You *must* perform the NAT on the machine Squid is running on for
> > intercept mode to work.
> >
> > Doing it on any other router along the way will not work.
>
> Unless I'm missing something, I'd phrase this differently: the
On 15/01/2016 6:25 a.m., Robert Plamondon wrote:
>>
>>
>> You *must* perform the NAT on the machine Squid is running on for intercept
>> mode to work.
>>
>> Doing it on any other router along the way will not work.
>>
>
> Unless I'm missing something, I'd phrase this differently: the NAT must not
>
>
> You *must* perform the NAT on the machine Squid is running on for intercept
> mode to work.
>
> Doing it on any other router along the way will not work.
>
Unless I'm missing something, I'd phrase this differently: the NAT must not
be performed between the client and Squid. Squid is indiffer
On 15/01/2016 1:27 a.m., Antony Stone wrote:
> On Thursday 14 January 2016 at 13:21:57, jean-yves boisiaud wrote:
>
>> My squid box is not on a firewall, but on a dedicated server in the DMZ,
>> between the internal and the external firewall.
>
>> On the internal firewall, port 80 is redirected t
On Thursday 14 January 2016 at 13:21:57, jean-yves boisiaud wrote:
> My squid box is not on a firewall, but on a dedicated server in the DMZ,
> between the internal and the external firewall.
> On the internal firewall, port 80 is redirected to the squid box port 3128,
> for transparent proxying.
hello,
I am migrating a squid box from squid 2.7 to squid 3.4.8 (debian jessie).
I use squid for forwarding only.
My squid box is not on a firewall, but on a dedicated server in the DMZ,
between the internal and the external firewall.
So, I have two http_port directives :
http_port 8080
http_p
