On 05/12/14 14:22, Amos Jeffries wrote:
One is a HIT the other a MISS?
Squid ACLs?
TCP connection issue?
Found the problem. We had three proxies and the Cisco ASA was load
balancing between them. Ended up the 2nd proxy had INPUT DROP instead
of INPUT ALLOW in iptables (everything else being
Hello,
I'm working with some scripts to prefetch content but having some
trouble, what I can't work out is a way to check if a given object is
already cached, in other words, I want to check if the object I'm going
to download is going to hit, in which case I can ignore it.
I've read
Hi Eliezer,
The command for www.google.com failed to complete the connection with a unknown
protocol error:
openssl s_client -connect www.google.com:443 -showcerts
CONNECTED(0003)
140623996839752:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown
protocol:s23_clnt.c:766:
---
no
Hi ,
I have a Kerberos protected website. I am making a Kerberos enabled browser.
I need to test my browser for proxy support.
At least, I must do these 2 tests:
1. make some of my servers only accessible via a proxy (to test my
software's proxy support)
2. have the proxy require
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/12/2014 6:04 a.m., Ulises Nicolini wrote:
Hello,
I'm working with some scripts to prefetch content but having some
trouble, what I can't work out is a way to check if a given object
is already cached, in other words, I want to check if
Hello,
we use squid 3.4.9 as proxy for our company with ipv4 and ipv6 dual
stack.
It works good, but if a destination has an A and record and the
webserver isn't reachable via ipv6, squid generates an error page
instead of trying a connection via ipv4.
One example is the url:
Yeap, squid perfectly splice the destination domain after step1 or
step2 or step3 when the browser is set to use proxy directly.
But, it does not work in case of transparent proxy. Squid uses the
destination IP address instead of SNI details.
The example of using client IP address is below:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey Glen,
Since openssls_client is showing you this error I assume squid
received the same response.
We do need to verify why the connection is being hangs.
For now it seems like not 100% squid related issue.
Eliezer
On 12/09/2014 01:57 AM,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/12/2014 4:48 a.m., Dieter Bloms wrote:
Hello,
we use squid 3.4.9 as proxy for our company with ipv4 and ipv6
dual stack. It works good, but if a destination has an A and
record and the webserver isn't reachable via ipv6, squid
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/12/2014 5:19 a.m., Stephen Young-Work wrote:
Hi, We have an upstream (parent) proxy that we have no control over
and I am trying to get squid to cache .ipa files and other large
updates.
I have tested this offsite where there is no proxy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Squid HTTP Proxy team is very pleased to announce the availability
of the Squid-3.4.10 release!
This release is a bug fix release resolving several issues found in
the prior Squid releases.
The major changes to be aware of:
* Bug 4033:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/10/2014 09:25 PM, HaxNobody wrote:
The proxy runs on Linux (Ubuntu, I believe), and I'm doing my
testing from multiple browsers on Windows 8.1. I have been unable
to find a way to use openssl s_client via a proxy, although I was
able to run
squid -v:
Squid Cache: Version 3.3.10
configure options: '--build=x86_64-linux-gnu' '--prefix=/usr'
'--includedir=${prefix}/include' '--mandir=${prefix}/share/man'
'--infodir=${prefix}/share/info' '--sysconfdir=/etc' '--localstatedir=/var'
'--libexecdir=${prefix}/lib/bloxx-squid3' '--srcdir=.'
13 matches
Mail list logo
