Hi All,
I'm Akhaice.
# And now, thanks for developers and maintainers at all times.
I'm using squid-3.5.16.
Recently I upgraded from squid-3.1 to squid-3.5.
And I've been using ICAP Server that has authentication function.
I configured that users needed authentication when they access web site.
On Thu, Aug 4, 2016 at 10:20 AM Alex Rousskov <
rouss...@measurement-factory.com> wrote:
> On 08/03/2016 08:45 PM, JR Dalrymple wrote:
>
> > To be brutally honest the whole concept is still a bit lost on me
>
> [rant]Admitting one's limitations is often the most difficult first
> step, but please
On 08/03/2016 08:45 PM, JR Dalrymple wrote:
> To be brutally honest the whole concept is still a bit lost on me
[rant]Admitting one's limitations is often the most difficult first
step, but please do not stop here! Suggestions for where to go next: Ask
good questions, do not accept answers you do
On 08/04/2016 10:08 AM, Heiler Bemerguy wrote:
Sorry Amos, but I've tested with modifying JUST these two sysctl parameters and
the difference is huge.
Without maximum tcp buffers set to 8MB, I got a 110KB/s download speed, and
with a 8MB kernel buffer I got a 9.5MB/s download speed (via squ
Sorry Amos, but I've tested with modifying JUST these two sysctl
parameters and the difference is huge.
Without maximum tcp buffers set to 8MB, I got a 110KB/s download speed,
and with a 8MB kernel buffer I got a 9.5MB/s download speed (via squid,
of course).
I think it has to do with the
Thanks for your patience with this, but still not quite getting it.
I thought there were two cases:
1) Client drops the connection before the interaction is complete ==
log shows HTTP result code 000, almost always size 0 as well;
2) Interaction completed successfully == HTTP result cod
On 4/08/2016 10:16 p.m., Garth wrote:
> Hi All
>
> I am struggling with delay pools and Group AD. I have managed to narrow
> down the problem to the AD Groups. If I do user auth, the delay pool
> works perfectly. I have tried multiple groups from old to new just
> incase. The AD Groups work for no
At what point does buffer bloat set in? I have a linux router with the
below sysctl tweaks load balancing with haproxy to 2 squid instances. I
have 4 x 1Gb interfaces bonded and have bumped the ring buffers on RX and
TX to 1024 on all interfaces.
The squid servers run with almost the same hardwa
On 4/08/2016 9:37 p.m., reinerotto wrote:
> I have the impression, that these squid versions are much more
> memory/CPU-hungry compared to good old 2.7
> Any users out there, to share some experience ?
Perhapse on CPU a little. The memory defaults have been raised since
even most embeded systems h
On 4/08/2016 9:52 p.m., Henry S. Thompson wrote:
> Amos Jeffries writes:
>
>> On 4/08/2016 2:36 a.m., Henry S. Thompson wrote:
>>> I'm trying to do some summary statistics based on log files from our
>>> 2.6.STABLE18 setup.
>>
>> Please upgrade. The current 3.5.20 release can do everything that
>>
I have the impression, that these squid versions are much more
memory/CPU-hungry compared to good old 2.7
Any users out there, to share some experience ?
I am running 3.5.20 on a 580MHz MIPS CPU, with 128MB RAM.
So my system is limited in many aspects, and I try some tuning.
For example, recent fi
Hi All
I am struggling with delay pools and Group AD. I have managed to narrow
down the problem to the AD Groups. If I do user auth, the delay pool
works perfectly. I have tried multiple groups from old to new just
incase. The AD Groups work for normal site access in the http_access
rules etc
Amos Jeffries writes:
> On 4/08/2016 2:36 a.m., Henry S. Thompson wrote:
>> I'm trying to do some summary statistics based on log files from our
>> 2.6.STABLE18 setup.
>
> Please upgrade. The current 3.5.20 release can do everything that
> Squid-2.6 could do, and a lot more useful stuff besides.
On 4/08/2016 2:36 a.m., Henry S. Thompson wrote:
> I'm trying to do some summary statistics based on log files from our
> 2.6.STABLE18 setup.
Please upgrade. The current 3.5.20 release can do everything that
Squid-2.6 could do, and a lot more useful stuff besides.
>
> A range of issues with inte
On 4/08/2016 8:15 p.m., reinerotto wrote:
> Thanx a lot, I got it now.
> The magic line in squid.conf, I had to add:
>
> acl safe_ports port 3128
>
Hmm. Which means you have altered the settings for Safe_ports in the
first place to be far too restrictive.
Safe_ports purpose and use in the basi
On 4/08/2016 8:04 p.m., Harsha S Aryan wrote:
> this is my squid conf file.
>
> #
>
> auth_param basic children 5
> auth_param basic realm Squid proxy-caching web server
> auth_param basic credentialsttl 2 hours
> auth_param basic casesensitive off
> ac
Thanx a lot, I got it now.
The magic line in squid.conf, I had to add:
acl safe_ports port 3128
Now
http://my.local.ip.onsquidbox:3128/squid-internal-mgr/info
succeeds.
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/cachemgr-cgi-on-embedded-system-tp46
this is my squid conf file.
#
auth_param basic children 5
auth_param basic realm Squid proxy-caching web server
auth_param basic credentialsttl 2 hours
auth_param basic casesensitive off
acl allowed_sites dstdomain "/etc/squid3/Allowed_Sites.txt"
acl bl
18 matches
Mail list logo
