Thanks for the explanation. It makes sense.
I'll wait for squid 3.4 to be officially released.
Cheers
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-RP-in-front-of-Atlassian-Stash-with-SSL-100-CPU-and-not-responding-tp4661490p4661501.html
Sent from t
Hi Amos,
please let me know how to get your patch related to the above.
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/icp-query-timeout-directive-is-not-working-in-3-3-8-for-some-reason-tp4661324p4661500.html
Sent from the Squid - Users mailing list archiv
On 9/08/2013 2:04 p.m., Romeo Mihalcea wrote:
I just upgraded to squid 3.3.8 to take advantage of the workers and
split the load between CPUs. Since I never worked with workers and the
documentation or examples are lacking I thought I start by simply
adding workers 2 to my config.
http://wiki.s
On 9/08/2013 1:53 p.m., Roberto Carna wrote:
Dear, I have implemented a Splash page with Debian 7 + Squid 3.1 as folow:
external_acl_type splash_page ttl=60 concurrency=100 %SRC
/usr/local/sbin/squid/squid_session -t 7200 -b
/var/lib/squid/session.db
acl existing_users external splash_page
den
I just upgraded to squid 3.3.8 to take advantage of the workers and
split the load between CPUs. Since I never worked with workers and the
documentation or examples are lacking I thought I start by simply
adding workers 2 to my config.
Squid start with no error but the clients can't connect to the
Dear, I have implemented a Splash page with Debian 7 + Squid 3.1 as folow:
external_acl_type splash_page ttl=60 concurrency=100 %SRC
/usr/local/sbin/squid/squid_session -t 7200 -b
/var/lib/squid/session.db
acl existing_users external splash_page
deny_info http://example.com/splash.html existing_
Hello there!
I installed a TPROXY squid V3.3.7 for a client who originally had an intercept
squid V2.7.STABLE9. The request hit ratio of the old squid server is around 35%
and byte hit ratio is around 10%. For some reason, the client wanted to keep
the original squid server, but he connected it
Hello,
I'm having the following issue.
My network have about 15 AD domain controllers. When
ext_kerberos_ldap_group_acl is used, according to the help page, it
operates doing:
" ext_kerberos_ldap_group_acl will determine automagically the right
ldap server.
The following method is used:
1
On 8/08/2013 11:38 p.m., Alfredo Rezinovsky wrote:
El 07/08/13 16:02, Roman Gelfand escribió:
Is there a way I could control access to various sites based on user
irregardless of workstation they are on? All in transparent proxy.
Thanks in advance
I did this a long time ago.
I had a termina
El 07/08/13 16:02, Roman Gelfand escribió:
Is there a way I could control access to various sites based on user
irregardless of workstation they are on? All in transparent proxy.
Thanks in advance
I did this a long time ago.
I had a terminal server, so all the users came from the same IP.
I
On 8/08/2013 8:04 p.m., PSA wrote:
I've been stuck on this for 2 days now.
After accessing this cache a couple of times, the CPU jumps to 100% and
squid stops forwarding requests.
It remained like this for 24 hours until I killed the process.
Adding the following lines to the config has res
I've been stuck on this for 2 days now.
After accessing this cache a couple of times, the CPU jumps to 100% and
squid stops forwarding requests.
It remained like this for 24 hours until I killed the process.
Adding the following lines to the config has resolved the issue:
###
12 matches
Mail list logo
