Dear Fellow,
I am implement a Distributed cache system (1 child Proxy, 2 parent proxy as
sibling).
in the cache peer algorithm, I use Weighted Round-Robin.
But when I analyze the log using Squeezer, I am found that there is no hit
requestin the parent proxy.
I have attached the conf (Child.
This time I'm writing not to ask for help, but to give something back.
As we received much help from this mail list during our migration from
Squid 2.7 to 3.x and in the proccess we had to make some modifications
to jesred (helper) to make it compatible with Squid, we have decided to
start a ne
On 12/05/2015 2:28 a.m., Stakres wrote:
> Hi Amos,
>
> OK, got it.
> But why a so big gap on the 2 parents ?
> The 3 squids are on the same range, connected to the same switch, all in 1Gb
> NIC.
> No problem if there are some MB difference, but here it's 10+ times more
> between 2 parents
Only
Hi Amos,
OK, got it.
But why a so big gap on the 2 parents ?
The 3 squids are on the same range, connected to the same switch, all in 1Gb
NIC.
No problem if there are some MB difference, but here it's 10+ times more
between 2 parents
Bye Fred
--
View this message in context:
http://squid-web
On 12/05/2015 12:01 a.m., Stakres wrote:
> Hi All,
>
> A crazy thing I cannot understand:
> - 3 squid 3.5.4
>
> the child (172.10.1.1) is like that:
> cache_peer 172.10.1.2 parent 8182 8183 proxy-only weighted-round-robin
> background-ping no-tproxy
> cache_peer 172.10.1.3 parent 8182 8183 proxy-
On 11/05/2015 11:27 p.m., Ambadas Hibare wrote:
> Hi,
>
> The problem is many clients are already preconfigured with proxy ip/port
> settings due to previous setup.
>
huh? your "problem" is that clients are setup correctly?
TPROXY and NAT interception (aka. hjacking attack on users) are the
*h
Hi All,
A crazy thing I cannot understand:
- 3 squid 3.5.4
the child (172.10.1.1) is like that:
cache_peer 172.10.1.2 parent 8182 8183 proxy-only weighted-round-robin
background-ping no-tproxy
cache_peer 172.10.1.3 parent 8182 8183 proxy-only weighted-round-robin
background-ping no-tproxy
ICP is
Hi,
The problem is many clients are already preconfigured with proxy ip/port
settings due to previous setup.
If you don’t mind, may I know like its squid's feature, or the Linux OS
feature, which doesn’t do transparency only towards web server?
Regards,
Ambadas
-Original Message-
Fr
I think, this is requirement for invisible proxy, Amos
11.05.15 16:30, Amos Jeffries пишет:
On 11/05/2015 5:56 p.m., Ambadas Hibare wrote:
Hi Amos,
But in my requirement, the clients are configured with Squid IP & Port. Is there any
possible way/approach by which I can make "Squid IP" hide to
On 11/05/2015 5:56 p.m., Ambadas Hibare wrote:
> Hi Amos,
>
> But in my requirement, the clients are configured with Squid IP & Port. Is
> there any possible way/approach by which I can make "Squid IP" hide towards
> web server?
>
No. Hiding the Squid IP in the TCP/IP layers without full TPROX
10 matches
Mail list logo
