ither caching problem at that point? Would that
solve problem #1 without taking any further action? At that point, how
hard would it be to implement ssl-bump?
Thanks,
John
On Thu, Nov 5, 2015 at 7:31 AM, Amos Jeffries wrote:
> On 5/11/2015 7:16 a.m., John Smith wrote:
> > Hi,
> &g
Hi,
I'm trying to improve our cache hit ratio. We have a fairly complicated
layer of squid 3.10 proxies as previously detailed.
Problem 1. Some of the traffic is identified by domain to go to another
layer of proxies. I've called this proxy otherl1proxy in the squid.conf
below. I've noticed t
ogged as 'noise'. Still quite an
improvement.
Thanks Amos and Eliezer for reaching out!
John
On Thu, Oct 29, 2015 at 2:31 PM, Amos Jeffries wrote:
> On 30/10/2015 9:51 a.m., John Smith wrote:
> > The outbound traffic from the L1proxy instance in question connects to a
>
ng DNS to connect to them.
I'm not exactly certain how the ELB functions, at least I don't know enough
to answer your question.
The healthcheck and listeners are are TCP, not HTTP.
On Thu, Oct 29, 2015 at 1:19 PM, Amos Jeffries wrote:
> On 30/10/2015 8:39 a.m., John Smith wrote:
>
;t need
> intercept*
>
> By the way, have you tried haproxy instead of squid? I think it will might
> be better suited for this specific issue.
>
> All The Bests,
> Eliezer
>
>
> On 29/10/2015 16:08, John Smith wrote:
>
>> Hi Amos and Eliezer,
>>
&
verify if you need a http_port or http_port accel
> > or http_port 1111 intercept.
> >
> > I will be glad to help you in about 20 hours.
> >
> > Eliezer
> >
> > On 29/10/2015 02:06, John Smith wrote:
> >> Hi Eliezer,
> >>
&g
Hi Eliezer,
I've added a single line to my squid.conf:
http_port 3130
And I've modified my AWS ELB healthcheck to monitor port 3130 instead of
3128.
Now my instances are still in the ELB, and the proxy still works as
expected, AND the amount of garbage errors in the cache.log has been
significant
specific
> issue or something else.
>
> All The Bests,
> Eliezer
>
>
> On 29/10/2015 00:51, John Smith wrote:
>
>> hi,
>>
>> I have a working(?) squid 3.10 proxy configuration.
>> squid-3.1.10-29.18.amzn1.x86_64 on AWS Linux behind an AWS elastic load
hi,
I have a working(?) squid 3.10 proxy configuration.
squid-3.1.10-29.18.amzn1.x86_64 on AWS Linux behind an AWS elastic load
balancer.
My problem is that it appears every single AWS elastic load balancer
healthcheck triggers a line like this in cache.log:
2015/10/28 22:35:10| IpIntercept.cc(13
