-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/10/2014 1:19 a.m., Michele Bergonzoni wrote:
I have an external ACL defined as: external_acl_type preauth
cache=0 children-max=1 concurrency=100 ttl=0 negative_ttl=0 %SRC
%{User-Agent} %URI %METHOD /usr/sbin/squid-preauth
It is well known
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/10/2014 4:12 a.m., Amos Jeffries wrote:
On 5/10/2014 3:34 a.m., Omid Kosari wrote:
Mehdi Sarmadi wrote
Hey
Alright. About refresh pattern you have a very excessive list
IMHO. I don't know about your hardware but generally for a
typical
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/10/2014 5:36 a.m., John Gardner wrote:
Eliezer
It would be be great if you could manage to do a build 64bit OEL 6
build this week, but I understand you will be under great time
pressure, so I will also try and perform a build from the SRPM
of
the certificte chain as necessary.
On Sun, Oct 5, 2014 at 8:52 AM, Eliezer Croitoru wrote:
On 10/05/2014 01:22 PM, Amos Jeffries wrote:
MSIE 11 seems to be growing in popularity for some reason
;-)
Amos
And Still there is:
http://bugs.squid-cache.org/show_bug.cgi?id=4115
For now I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/10/2014 9:01 p.m., Omid Kosari wrote:
Dear Amos
What's your idea about Marcus comment ?
It was a new solution to me.
I think I understand the details behind it (unicode charset size) and
agree it is worth doing if you can.
Amos
I should work, I recently used exactly that type of config with a client.
Can you try to use the latest stable (3.4.8) please, and add
debug_options, 28,3 to your squid.conf for a trace of what ACLs are
being checked.
Amos
On 8/10/2014 9:53 a.m., Ahmed Allzaeem wrote:
I just have one final
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/10/2014 4:19 a.m., Mirza Dedic wrote:
Thanks Amos, It seems I spoke too fast, the proxy prompt is back,
so disabling SG didn't do the trick.
Replying with a config file audit separately so it does not get lost
in the technical details of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/10/2014 2:28 a.m., Juan Manuel Perrote wrote:
I have a Squid Cache: Version 3.1.19, on Ubuntu 12.04.2 LTS.
We use external authentification on ldap repository on a remote
machine
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/10/2014 9:44 p.m., masterx81 wrote:
Nothing to do, seem that if squid fails one of the
negotiate_wrapper methods doesn't use any other method, asking that
password (that as you say isn't a basic auth, as the realm part
isn't displayed). In
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/10/2014 5:00 a.m., Josep Borrell wrote:
Hi,
I'm trying build a squid server that can cache youtube request for
a school. I'm using squid 3.4.7 compiled from source on Ubuntu
server 14.04 I have a lot of request that are cached, but not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/10/2014 9:14 p.m., 李志-iie wrote:
Hi,
I’m trying to set up Squid on a ARM platform. After compiling, I
run Squid with command “/opt/squid/sbin/squid -N -d1” , and then
configure the iptables. Unfortunately, when I browse a url, Squid
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks for the details on where to find Cygwin builds of Squid. I have
updated our wiki entry for Windows to include that.
As for the mskutil problems, you should not have to be patching at
all. Please contact the mskutil developers / support about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
May be related to a similar listing we got in their SafeWeb product
about a month ago.
That was due to one of the developer pages on the site being used to
host downloadable Squid management scripts. For some unknown reason
Norton flagged them as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14/10/2014 10:26 p.m., Robert Hundley wrote:
Hi, I'm trying to use squid to do some basic filtering. I have
added an ACL to filtering based on regular expressions, and added
in a few strings I'd like not to load. These work correctly on IE
and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15/10/2014 12:20 a.m., Satish Thareja wrote:
Hi,
I trying to get a video cached wherein the client sends a range
request for the video object(Range: bytes=36798-103701442) which
gets converted to request without range(range_offset_limit set
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15/10/2014 1:16 a.m., Satish Thareja wrote:
Hi Amos,
The client is being served the content as per the range in the
request headers. The object is cacheable and there are no other
caches involved.
The client requested range :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15/10/2014 7:14 a.m., Thiago Farina wrote:
Hi squiders,
We want to move the following Go code into squid, as we already
have squid in front of our Go server.
The code is:
func makeResourceHandler() func(http.ResponseWriter,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15/10/2014 5:01 a.m., Mirza Dedic wrote:
You should be able to grab SQUID 3.3.3 from Cygwin and compile it
there without issues. When working within cygwin get the cygport
program as there is a specific squid.cygport install file that
extracts
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please add -d to your parameters. That will output debug info into
cache.log for the lookups that may help you narrow down the problem.
For the record the helper manual is here:
http://www.squid-cache.org/Versions/v3/3.4/manuals/basic_ldap_auth.html
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
And the key difference in these configs is not the ACL contents, but
the ordering in which they are matched.
Mirzas' config starts by telling Squid everything on the LAN/localnet
is allowed. Ok, fine, Squid will do that.
Walters' config will tell
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16/10/2014 12:36 a.m., Jacques Kruger wrote:
Thanks for the information.
I'll do some further testing and confirm that the CPU isn't the
bottleneck in this case. The machine is a bit long in the tooth but
with the faster connection this could
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16/10/2014 7:23 a.m., Mirza Dedic wrote:
Thanks Walter and Amos, i've taken your advice and now I got the
blocking to partially work. I've re-organized how my ACLs are setup
(order) and using your examples Walter to implement my ACLs.
Working
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16/10/2014 6:03 p.m., santosh wrote:
Hello Amos,
Thanks for your reply , is there a way to prompt for
reauthentication if an browsing session is inactive by setting the
TTL value ? .
You are getting yourself into trouble by confusing the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16/10/2014 9:29 p.m., santosh wrote:
Hello Amos,
I'm just trying to create forceful re-authentication , this is just
for curiosity to see how things works by changing the
credentialsttl value in the conf file .I have set it as 2 mnutes
and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16/10/2014 9:13 p.m., apfelstrudel wrote:
Hello. I am trying to get ssl-bump to decrypt https traffic
transparently so that I could filter out adult videos from youtube
and to globally enforce google safesearch on my network with
diladele web
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17/10/2014 8:10 a.m., Darren Spruell wrote:
Had a use case to ask about, apologies if I missed in docs. Is
there a configuration that allows squid running as forward proxy to
add a custom response header containing the origin server IP
address
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17/10/2014 9:29 a.m., Darren Spruell wrote:
On Thu, Oct 16, 2014 at 12:40 PM, Amos Jeffries
squ...@treenet.co.nz wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
On 17/10/2014 8:10 a.m., Darren Spruell wrote:
Had a use case to ask about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17/10/2014 3:35 a.m., daniel.rie...@gmx.net wrote:
Hi guys,
I got a problem with DEAD Parent detection. I've configured 2
parents in squid.conf:
cache_peer 10.0.0.101 parent 3128 0 default name=TEST1 cache_peer
10.0.0.102 parent 3128 0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17/10/2014 1:30 p.m., Robert Watson wrote:
I believe my problem relates to a previous post regarding TLS
fallback
http://www.mail-archive.com/squid-users%40squid-cache.org/msg95916.html
in the squid-users list. Has there been any progress with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17/10/2014 7:24 p.m., Alexander Samad wrote:
Hi
I am trying to reconfig the ssl setup on a reverse proxy set
https_port 2.7.3.1:443 accel
cert=/etc/httpd/conf.d/office.xyz.com.crt
key=/etc/httpd/conf.d/office.xyz.com.key
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17/10/2014 9:47 p.m., James Harper wrote:
Just reading up on this, the Feature page
http://wiki.squid-cache.org/Features/SslPeekAndSplice says:
... with Squid shoveling TCP bytes back and forth without any
decryption
I can't see that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17/10/2014 10:36 p.m., Ding Guigeng wrote:
hi guys! i had install squid 3.4.7 on centos 6.5. i defined acls
like below: acl worktime1 MTWH 8:00-12:00 acl worktime2 F
13:00-18:00
http_access deny !worktime1 http_access deny !worktime2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18/10/2014 8:47 a.m., Luderitz Bob wrote:
I have one central Proxy Server running Squid 3.1.10 under CentOS
6.3 running locally here and also for our 2 remote sites for all
http traffic.
We are using Cisco's WCCP and between the remote sites
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18/10/2014 8:56 p.m., Josep Borrell wrote:
Hi,
We are using a 3.4.8 squid Proxy in intercept mode via wccp. Squid
intercepts HTTP and HTTPS via ssl_bump. All is working fine except
that Windows Machines can't do a Windows Update. It is not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
That is a bug. Please add to bugzilla.
Amos
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)
iQEcBAEBAgAGBQJURCItAAoJELJo5wb/XPRjtgkIAKyGuSZQnpfofxeH5VggQ/sJ
2coDiglI/rVFjO4UAaCIu3e8Vhzst7cDmWaCbY9Gre6pemlliHuX2+64TmlzPcNv
/Download/http-mirrors.html
http://www.squid-cache.org/Download/mirrors.html
If you encounter any issues with this release please file a bug report.
http://bugs.squid-cache.org/
Amos Jeffries
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)
iQEcBAEBAgAGBQJURepmAAoJELJo5wb/XPRjke8H
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21/10/2014 6:25 p.m., Riccardo Castellani wrote:
I'm using Squid and it's unique access to go out to Internet. I
created rules for Skype traffic but I'd like to understand how to
set its ports because my unique access way to Intenret is proxy on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21/10/2014 6:55 p.m., saleh madi wrote:
Hello,
I have compiled squid 2.7stable9 with TPROXY patch, but the TPROXY
seem not working.
Er, yes. The TPROXY patch is not a Squid patch, it is a Linux kernel
patch adding TPROXY/cttproxy support to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21/10/2014 7:36 p.m., saleh madi wrote:
Hello Amos,
Many thanks for your reply. Before two years I have tested squid
2.7 it's very stable and in the high http traffic request is very
stable no crash. But for squid-3 I see too many different
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21/10/2014 8:52 p.m., lionx...@gmail.com wrote:
Hi. I‘m coming again.
Now, I have compiled squid-3.3.3 with --enable-ecap option
successfully on cygwin and run it successfully on windows. But,
there are another question about compiling
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21/10/2014 9:32 p.m., saleh madi wrote:
Hello Amos,
For squid 3.4.8, In the server we have 2xssd 240GB and 4XHDD
2000GB, Internet bandwidth 600Mbits and four squid instances,
please what is the suggestion settings for cache_dir for SSD and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/10/2014 5:40 a.m., Mike wrote:
I was reading through the release notes for squid 3.5, and in
section 2.4 regarding HTTPS, it mentions When Squid is built with
the GnuTLS encryption library the tool is able to open TLS (or
SSL/3.0)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/10/2014 5:11 a.m., Eugene M. Zheganin wrote:
Hi.
Is someone getting this too ? I get this with sad regularity:
# grep lm_request /var/log/squid/cache.log 2014/10/06 14:32:12
kid1| assertion failed: UserRequest.cc:229: lm_request-waiting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/10/2014 10:41 p.m., Eliezer Croitoru wrote:
On 10/22/2014 12:38 PM, Yassin CHOUCHANE wrote:
i have added on my squid.conf this ACL :
acl NoCachedSites dstdomain srv-java.e.t acl our_servers src
2.10.3.1
i have added the ip of
October 2014 11:45, Eliezer Croitoru elie...@ngtech.co.il
wrote:
On 10/21/2014 08:08 AM, Amos Jeffries wrote:
The Squid Software Foundation is very pleased to announce
the availability of the Squid-3.5.0.1 beta release!
I am not sure about what file is this release is in? Can you refer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23/10/2014 5:53 p.m., Victor Sudakov wrote:
Eliezer Croitoru wrote:
And about the basic issues that you were having with performance,
does it help to run Kerberos instead of NTLM (it should...)?
I have even moved squid to a new virtual
. And for the mention as well.
Amos Jeffries
Squid Software Foundation
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)
iQEcBAEBAgAGBQJUSIxjAAoJELJo5wb/XPRjlYEH/jotxE77CVkvs14ofu3NVy90
qMxih6siR7Vv5YPhWk3pG+Lf1axQwiMa9lZ3DY0SzPvQLfqAdDdGualpreI9ECMm
RBLQIhdBQsF3fhu+Xxb+UoNKzje
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23/10/2014 7:27 p.m., Victor Sudakov wrote:
Victor Sudakov wrote:
And about the basic issues that you were having with
performance, does it help to run Kerberos instead of NTLM
(it should...)?
I have even moved squid to a new virtual
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28/10/2014 12:17 a.m., saleh madi wrote:
Hello,
I have in the same box four squid 3.4.8 instances, I'm not using
the workers Option. I will need to peering the multiple instances
together to avoid duplication of objects. The below setting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28/10/2014 1:01 a.m., Amos Jeffries wrote:
On 28/10/2014 12:57 a.m., Jorge Visentini wrote:
Hello!
Sorry my english.
I'm racking my brain to figure out why the error.
I've used a long time ago a rule delay pool but this time I am
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/11/2014 1:39 p.m., Marcus Kool wrote:
On 10/31/2014 10:12 PM, Amos Jeffries wrote: On 1/11/2014 12:09
p.m., Marcus Kool wrote:
With OpenSSL 1.0.1e-fips :
openssl s_client -connect www.taxdisc.service.gov.uk:443
fails (tries TLS1.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/11/2014 6:39 p.m., Joel Mestres wrote:
hello everyone! I'm trying to configure squid 2.7 so it works with
a web server (another machine different from squid proxy server)
running apache2 on port 8082 (for instance). Squid is installed on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3/11/2014 12:56 a.m., Ahmed Allzaeem wrote:
Hi all ,
Sofar im using squid 3.4.3 with only ram caching ,..no cache_dir
configured
But...
traffic out is less than traffic in with squid 3.4.3 , is that not
good ?
from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3/11/2014 11:12 a.m., James Lay wrote:
A weird questionI guess I need to find out exactly what I'm
wanting before going further with trying to get peek to work. So
here's a small example of what I currently have. From my .conf
file:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3/11/2014 7:35 p.m., Avery_GoodMan wrote:
Hi All,
At the very outset , I would like to state that I have only
recently started administering a squid Proxy Server( 3 months) so
any omissions may pls be condoned. The problem I am facing is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3/11/2014 11:03 p.m., Avery_GoodMan wrote:
Hi Amos,
Thank you for your reply.
I did go through the access.log file but the log entries are
nothing unusual. a lot of TCP_DENIED requests ..etc. What intrigues
me is the high
please file a bug report.
http://bugs.squid-cache.org/
Amos Jeffries
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)
iQEcBAEBAgAGBQJUWFlsAAoJELJo5wb/XPRjii8IAJFGBJspa2AFDtWAh+/eddql
xOVCiyqzA2aSM4uMMjlJJNOiwdfgZjgRbEuv2cOrzajvm/ynR5poN0ZE1UKEzZvN
/
or the mirrors. For a list of mirror sites see
http://www.squid-cache.org/Download/http-mirrors.html
http://www.squid-cache.org/Download/mirrors.html
If you encounter any issues with this release please file a bug report.
http://bugs.squid-cache.org/
Amos Jeffries
-BEGIN PGP SIGNATURE-
Version
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/11/2014 10:39 p.m., navari.lore...@gmail.com wrote:
Good day today. I' m configuring a Squid Web Proxy Cache and I
apply the deny policy to some sites l this is the problem:
when people accesses sites with GET they have the right html error
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/11/2014 2:33 p.m., doc.holli...@usa.com wrote:
I've searched through the internets and tried various things... to
no avail. Hopefully someone here can point me in the right
direction. I am sitting behind a proxy, which accepts http/https.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/11/2014 8:58 p.m., Riccardo Castellani wrote:
I'm installing new machine as Squid server and I need to understand
what criteria to estimate the 'cache size', I'm not speaking about
extra space for swap/temporary files or fragmentation but I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/11/2014 10:20 p.m., Riccardo Castellani wrote:
Can I bypass this TCP_DENIE/D411 error in Squid? I read this
error is about Length Required field but we can permit Squid can
handle this request POST ?
If you send a message without saying how
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/11/2014 11:04 p.m., sq...@icshk.com wrote:
Hi Amos,
The configuration I post last time still cannot accomplish the
tasks.
I said the task was not possible.
You are trying to decide whether to authenticate, based on details
that will not be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/11/2014 3:57 p.m., Neddy, NH. Nam wrote:
Hi, I was going to download new tar ball of 3.5 beta but the whole
website is down now. Does anybody know any mirror?
These two are working:
http://www.eu.squid-cache.org/
http://west.squid-cache.org/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/11/2014 8:53 p.m., Riccardo Castellani wrote:
I think the request is http/1.1 because I captured it and it shows
in the 'Hypertext Transfer Protocol' in the POST section, the field
'Request version' is HTTP/1.1 I understand Squid 2.7 is not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/11/2014 12:08 a.m., Jatin Bhasin wrote:
Hello,
I am using squid 3.4.9 and the Dropbox client does not work with
SSLBump feature of squid. Dropbox client gives a message that it
cannot make a secure connection. Does anyone know fix or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/11/2014 4:12 a.m., Rietzler, Markus (RZF, SG 324 /
RIETZLER_SOFTWARE) wrote:
-Ursprüngliche Nachricht- Von: squid-users
[mailto:squid-users-boun...@lists.squid-cache.org] Im Auftrag
von Amos Jeffries Gesendet: Montag, 10. November
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/11/2014 1:37 a.m., Efe wrote:
I tried on different browser but it's the same. Clearing browser
cache and stopping the service made no difference either. I don't
know if Squid does change Ubuntu network settings. Any particular
place/file to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/11/2014 4:06 a.m., Job wrote:
Hello Elizier,
first of all thank you for your patience and help! I use this
directives in iptables:
iptables -t nat -A PREROUTING -p tcp --dport 80 -j REDIRECT
--to-port 3128 (for http) iptables -t nat -A
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/11/2014 9:28 a.m., Oleg Chomenko wrote:
Hello,
We use a squid cache for our robots to collects an information
from client's web sites.
The squid running on FreeBSD 9.3 , squid version 3.3.13
the configuration is like this:
if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/11/2014 5:40 a.m., Job wrote:
That means in your case avoid directly connecting to the
intercepting port. Connect to port 80/443 on some Internet server
instead and see
if the packets are properly delivered through Squid.
Also, avoid telnet
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/11/2014 7:47 a.m., Peter Gross wrote:
Hi, I am a new user of Squid and would first like to thank the
developers for this excellent software. This is my first post to
the mailing list ... I have been tasked with setting up quite
restrictive
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/11/2014 5:49 p.m., Jason Haar wrote:
Hi there
I was reading this list about the issue with google.com and was
playing around - and I used telnet to connect directly to the
intercept ssl-bump port. End result was squid immediately went to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/11/2014 10:36 p.m., Rafael Akchurin wrote:
Hello all,
I am struggling to compile Squid 3.5 on windows 7 x64 using latest
Cygwin.
During configuration (./configure --disable-wccp --disable-wccpv2)
NP: the current 3.5 should need NO
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13/11/2014 12:17 a.m., Hussam Al-Tayeb wrote:
Hello. I have a problem with 'squidclient -m PURGE' and also the
purge command. They won't purge urls from disk that are not
available online anymore or redirect to other links.
PURGE was designed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13/11/2014 1:55 a.m., Hussam Al-Tayeb wrote:
On Thursday 13 November 2014 01:39:27 Amos Jeffries wrote:
On 13/11/2014 12:17 a.m., Hussam Al-Tayeb wrote:
Hello. I have a problem with 'squidclient -m PURGE' and also
the purge command. They won't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13/11/2014 11:55 a.m., Ahmed Allzaeem wrote:
Hi all
I have two proxies
1(tproxy) and configured it to get from another normal proxy
So , my topology is as below
Tproxy- listen on 6000---normal proxy listen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13/11/2014 3:04 a.m., Hussam Al-Tayeb wrote:
On Thursday 13 November 2014 02:23:12 Amos Jeffries wrote:
On 13/11/2014 1:55 a.m., Hussam Al-Tayeb wrote:
On Thursday 13 November 2014 01:39:27 Amos Jeffries wrote:
On 13/11/2014 12:17 a.m., Hussam
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13/11/2014 11:55 a.m., Jason Haar wrote:
Hi there
I just found I cannot connect to https://www.bnz.co.nz/ using curl
on Ubuntu (7.35 compiled against openssl-1.0.1f), whereas
https://www.kiwibank.co.nz/ works fine. I first thought it was due
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13/11/2014 2:07 p.m., andrew williams wrote:
Hi, I'm getting what I think is too low of MEM_HIT ratio.. I would
like squid to use all of the cache_mem, thus increasing MEM_HIT?
You are running a 32-bit build of a Squid version deprecated more
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13/11/2014 3:22 p.m., Jason Haar wrote:
On 13/11/14 15:04, Amos Jeffries wrote:
Sounds to me like they are using SSLv3 in their server.
Yes but openssl s_client -tls1 also works, it just appears that
openssl cannot negotiate it - it has
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13/11/2014 7:39 p.m., Ahmed Allzaeem wrote:
Hi amos
I have changed the both hostnames on two servers :
[root@tproxy ~]# hostname tproxy.com
[root@parent ~]# hostname parent.com
Good.
but , as I told u last time I can see traffic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/11/2014 9:55 p.m., Job wrote:
Thank you Amos, for everything.
I route with REDIRECT all outgoing connection to port tcp/443 from
my LAN:
iptables -t nat -A PREROUTING -p tcp --dport 443 -j REDIRECT
--to-port 3130
in squid, i have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/11/2014 12:25 p.m., dan wrote:
Bumping this with another backtrace. Happened at 16:05 this time,
when the system was not very very busy.
It’s causing squid to crash in such a way that I actually have to
`kill -9` the process in order to get
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13/11/2014 9:39 p.m., jcourtois wrote:
Hi everyone,
I've been trying to create a simple encrypted connexion in between
a browser (that support https proxy connexion, I use Firefox 33 to
do my test because it's supose to support it:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14/11/2014 10:36 a.m., Hector Chan wrote:
Basically, what I am looking for is whether it's possible to set up
the following:
Client (A) -- Squid as Reverse Proxy (B) -- Squid as Forward
Proxy (C) -- Origin Servers Depending on Client Request
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13/11/2014 10:10 p.m., Lorenzo Gollinelli wrote:
Thank you very much Amos,
why then do we have the problem only if file is 55kB? The bug
your are referring (#4067) to is not listed in version 3.4 known
bugs
I thinnks the size weirdness is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15/11/2014 3:41 a.m., Ulises Nicolini wrote:
HI All!!!
I'm building a system based on squid 2.7 for cache all software
updates.
Not possible. Squid-2.7 does not support enough HTTP/1.1 features to
cache all content properly. Upgrade to a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15/11/2014 5:21 p.m., santosh wrote:
Hello Team,
I have set-up squid proxy server with ldap authentication , the
infrastructure is setup in such a way that users have to access the
internet through the proxy .In Internet explorer there's an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15/11/2014 7:33 p.m., Victor Sudakov wrote:
Amos Jeffries wrote:
I have set-up squid proxy server with ldap authentication , the
infrastructure is setup in such a way that users have to
access the internet through the proxy .In Internet
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15/11/2014 9:03 p.m., Michael D. Setzer II wrote:
Normally, I would download the file on a machine locally, so it was
in the local squid servers cache, but now that it uses the ISPs
server as a parent, it didn't seem to cache the file on the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17/11/2014 2:24 a.m., Ahmed Allzaeem wrote:
Hi Amos , thank you
Really sorry to ask you , wts needed to be done to use largerock
support ?
Example 5GB rock cache;
cache_dir rock /ssd1 5000
I mean wt wring im doing ?
Also about the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16/11/2014 2:12 p.m., James Harper wrote:
I've written a little helper to do ssl callouts to determine if
the server is running ssl at all (eg not tunnelling over ssl), and
also to be able to do limited ACL on CN/SAN. The main limitation is
the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19/11/2014 12:30 a.m., schinken wrote:
Hi there,
i'm currently trying to do authentication against LDAP and NCSA
auth - but it looks like, the user is never checked against NCSA if
auth against LDAP failed (because the user doesn't exist):
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19/11/2014 4:39 p.m., Kendrick . wrote:
I am using centos7 with a 3.4 squid package. I have tried a
commercial and a couple user made url_rewrite_program items. They
have all not ran properly. I had to disable selinux as it was not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19/11/2014 6:59 a.m., Frank wrote:
Hi,
Since upgrading from 3.1.22 to 3.4.8 I have been unable to get the
transparent mode to accept my IP. I am seeing permission denied in
the transaction when I do a packet dump. I have read the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19/11/2014 10:36 p.m., santosh wrote:
Hello Team,
We have setup squid proxy server and the backend authentication is
through Open LDAP . each user is given with an unique id and
password . We have been tracking the logs for accessdenied
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19/11/2014 11:19 p.m., santosh wrote:
I have got fresh set of logs my username is spai and i 'm already
authenticated and one of the site www.flipkart.com is blocked and i
accessed it for testing purpose ,but the user name is still not
shown .
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20/11/2014 2:11 a.m., brendan kearney wrote:
Yes and it seems java is even more sensitive. I had an array
member defined on a line that was not terminated with a semicolon
and browsers did not throw errors, but java did. Pactester did not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21/11/2014 12:43 a.m., Andreas.Reschke wrote:
Von: Amos Jeffries
On 20/11/2014 10:57 p.m., Andreas.Reschke wrote:
Hi there,
we're using 3 squid proxy (version 3.3.-13, no caching, no
logging) at our LAN (4500 User) in front of a squid proxy
1 - 100 of 4714 matches
Mail list logo
