On 14/07/2014 5:29 p.m., Eugene M. Zheganin wrote:
Hi.
On 12.07.2014 14:16, Amos Jeffries wrote:
Sounds like http://bugs.squid-cache.org/show_bug.cgi?id=3966
PS. 3.3 series will never get this fix. It is on the TODO list for a
3.4.7 porting attempt, but the volatile SSL-bump related
On 15/07/2014 6:23 a.m., Edwin Marqe wrote:
Hi Eliezer,
I understand that, but this is pretty much the point of my e-mail. In
my company we don't work with servers installed physically here,
instead, we rent servers to a company. We use 2 nameservers for our
clients, and the IT company uses
Hi,
Im having some confusing trouble with an external acl based
reply_body_max_size setup, but only when the ext_log is brought into
things.
I have an external acl setup as such:
external_acl_type response_size_type ttl=300 children-startup=2
children-idle=1 children-max=10 %URI %EXT_LOG
On 15/07/2014 7:04 p.m., Cameron Charles wrote:
Hi,
Im having some confusing trouble with an external acl based
reply_body_max_size setup, but only when the ext_log is brought into
things.
I have an external acl setup as such:
external_acl_type response_size_type ttl=300
On 15/07/2014 5:42 a.m., Patrick Chemla wrote:
Hey Eliezer,
Happy to read you.
What do you call rock as cache_dir?
cache_dir of type rock. But that is not relevant here.
Here is squid -kparse
Besides lots of warnings about config file directives tat need to be
updated...
2014/07/14
Hi Eliezer,
I have disabled SELINUX, doesn't help.
shm partition is mounted OK from beginning
I can't find basic_data.sh, nor on my disk after install of squid
package or sources, nor using google.
I am trying to compile squid-3.4.6 to add rock cache type (not included
by default) but I get
Thanks for help.
The problem is that I can have some external IPs and hundreds ports
for each IP on the same box.
Up to now, I am using virtual machines for IPs and I route the ip:ports
with iptables to the right VM (hundreds ports each). There one squid
instance is listening to 128 ports
Hi Eliezer
I have found the solution.
I have change the option
forwarded_for from “off” to “delete and now it’s working(option via
off was ok).
I have resolved also the problem with streaming video (
06/17/2014 11:55 AM).
Thank you
Maurizio
Resolved.
Setting option:
via off
forwarded_for delete
Best regards,
Maurizio
On 15/07/2014 1:14 a.m., ama...@tin.it wrote:
Hello
I have a problem with
- squid-3.3.9
- squid-3.4.5
but NO
problem with:
- squid-2.7.stable9
- without proxy
I have tested with
firefox 24.6 and ie explorer 8.0.
On browser the error displayed is:
The following error was
I've seen a February thread about this problem, but it seems that it
never reached a consensus.
I've just tried to migrate from 3.3.12 to 3.4.6, but almost instantly
got timeout problems and 100% cpu usage by squid process.
I'm using kerberos auth and external_ldap_group helpers, ssl bump,
Try without delay_pool or at least without CONNECT method and delay_pool
Fred
delay_pools are not used at all (delay_access 1 deny all), i'll try to
remove them completely,
but as 3.3 works fine i doubt that'll help.
On 15.07.2014 19:01, FredB wrote:
Try without delay_pool or at least without CONNECT method and delay_pool
Fred
Hi there!
It's been years I haven't played around with squid so I wanted to make a
simple configuration just to see whether I remember the basic things,
and I found two problems:
I'm running:
# squid3 -v
Squid Cache: Version 3.3.8
1) My configuration is the default that the package
Hi there,
As stated in another thread, using the access log format st seems
ineffective to measure upload bandwidth to things like Google Drive.
Amos stated that this could be related to a CONNECT issue.
Is anyone aware of this issue? Is there a bug report?
Now the good news: I'm collecting
Regarding first issue:
Have a look here for a correct solution:
http://wiki.squid-cache.org/ConfigExamples/Intercept/AtSource
#Example for squid and NAT on same machine:
iptables -t nat -A OUTPUT -p tcp --dport 80 -j DNAT --to-destination
SQUIDIP:3128
#Replace SQUIDIP with the public IP which
Thanks! That would indeed cover the first issue :-) I initially used
redirect because somewhere I read that it's not a good idea forwarding
the traffic directly to the port where squid listens and it should be
pointed to another port instead and then redirected. However, working as
this, it
Thanks alot, this work around does indeed work, once the ACL itself
was modified to not alter the EXT_LOG the second time around, if i'm
understanding correctly when an acl result is cached the ext_log it
was passed is also cached essentially as part of the key used to
lookup the result in the
I have found that although RFC's state that you should have VIA and forwarded
for headers, firewalls and intrusion detection devices are now blocking (based
on their configuration of the organization) proxies that are detected using
these headers as the method for detection.
Best regards,
19 matches
Mail list logo
