On 26/06/2015 2:36 a.m., Mike wrote:
> Amos, thanks for info.
>
> The primary settings being used in squid.conf:
>
> http_port 8080
> # this port is what will be used for SSL Proxy on client browser
> http_port 8081 intercept
>
> https_port 8082 intercept ssl-bump connection-auth=off
> generate-
On 26/06/2015 4:36 p.m., Squid List wrote:
> Hi,
>
> Is the Squid can cache Microsoft Updates and IOS Updates?
>
> If its cache means, please help me out for cache Chrome OS updates in
> latest squid version that is installed in CentOS 6.6.
The short answer (FWIW):
Squid can (and does) cache an
Hi,
Is the Squid can cache Microsoft Updates and IOS Updates?
If its cache means, please help me out for cache Chrome OS updates in
latest squid version that is installed in CentOS 6.6.
Thanks & Regards,
Nithi
___
squid-users mailing list
squid-us
On 25/06/2015 6:49 p.m., YogiBearNL aka Ronald wrote:
> Squid v2.7:
>
> Jun 25 08:36:37 proxy SQUID[16271]:
> 192.168.2.85 - - [25/Jun/2015:08:36:37 +0200] "GET
> http://tpc.googlesyndication.com/safeframe/1-0-2/html/container.html
> HTTP/1.1" 200 2439 "http://tweakers.net/"; "Mozilla/5.0 (Macint
Amos, thanks for info.
The primary settings being used in squid.conf:
http_port 8080
# this port is what will be used for SSL Proxy on client browser
http_port 8081 intercept
https_port 8082 intercept ssl-bump connection-auth=off
generate-host-certificates=on dynamic_cert_mem_cache_size=16MB
Hi Eliezer,
it depends.
The problem is not the NAS/SAN per se, but the disk access patterns.
Squid's disk access pattern, regardless the technology, is always
randomly-timed 4kb writes (in case of Rock, they are sequential, in
*ufs scattered).
If the NAS/SAN uses a write-back policy, it is possib
Hi Tom,
How did you succeed in filtering https traffic? using http_access.. or
the way James did it, using domainname only ?
Tom Mowbray wrote on 06/25/2015 02:06 PM:
James,
Thank for for your help. Now that I have a better understanding of how
the https traffic is handled, I've been able t
On Thu, 2015-06-25 at 08:06 -0400, Tom Mowbray wrote:
> James,
>
>
>
> Thank for for your help. Now that I have a better understanding of
> how the https traffic is handled, I've been able to get things working
> as intended.
>
>
>
>
>
> -
>
> Tom Mowbray
>
Hello list,
I was wondering if someone has ever tried to use a SAN\NAS as the cache
backend?
Since rock cache type\dir changed the file handling way from "lots of
files db" into a single(and one more) cache db There is surly a way to
benefit from nas and SAN.
If someone have used san(ISCSI)
James,
Thank for for your help. Now that I have a better understanding of how the
https traffic is handled, I've been able to get things working as intended.
-
Tom Mowbray
*tmowb...@dalabs.com*
*703-829-6694*
On Wed, Jun 24, 2015 at 2:05 PM, James Lay wrote:
On Thu, 2015-06-25 at 13:57 +1200, Jason Haar wrote:
> On 25/06/15 06:05, James Lay wrote:
> > openssl s_client -connect x.x.x.x:443
> Just a FYI but you can make openssl do SNI which helps debugging (ie
> doing it your way and then doing it with SNI)
>
> openssl s_client -connect x.x.x.x:443 -s
On 25/06/2015 4:48 p.m., Hector Chan wrote:
> Not sure if this will help you, but I saw 503s on my squid when the origin
> server has an invalid SSL certificate -- expired cert, self-signed cert,
> etc.
>
Nod. They show up whenever Squid cannot successfully connect to the
server. Thats what "503
On 25/06/2015 12:45 p.m., Alex Samad wrote:
> Hi
>
> why this, doesn't this block all traffic getting to the squid port.
> iptables -t mangle -A PREROUTING -p tcp --dport $SQUIDPORT -j DROP
All external traffic yes. The NAT interception happens afterward and works.
The point is that NAT intercep
13 matches
Mail list logo
