I use this configuration parameters to build 64 bit 3.5.x Squid on Solaris:
'--prefix=/usr/local/squid' '--enable-translation'
'--enable-external-acl-helpers=none' '--enable-ecap'
'--enable-ipf-transparent' '--enable-storeio=diskd'
'--enable-removal-policies=lru,heap' '--disable-wccp'
'--enab
Hi All,
I have 2 issues
First one: How can i bypass proxy for an IP in LAN.
Second one:
I am running squid on openwrt and i want to allow some websites to bypass
proxy and want to allow them go direct.
For that i am using wpad with PAC file but the problem is for some websites
it works and for
Hello!
We're having serious problems with a squid proxy server.
The good news is the problem can be reproduced at any time in our production
squid system.
Environment:
- CentOS release 6.5 (Final) with Linux kernel 2.6.32-431.29.2.el6.x86_64
- squid-3.1.10-22.el6_5.x86_64 (a bit old, CentOS sh
Hello again!
Sorry for the typos, case #4 and case #5 are https tests, not http:
4. https-delaypool.pcap:
- wget -c https://www.opengroup.org/infosrv/DCE/dce122.tar.gz,
- delay pools are active
- HTTPS flows with 69 byte packets -> this is extremely bad
5. https-nodelaypo
Look into the pacparser project on github. It allows you to evaluate a pac
file and test the logic.
Hi All,
I have 2 issues
First one: How can i bypass proxy for an IP in LAN.
Second one:
I am running squid on openwrt and i want to allow some websites to bypass
proxy and want to allow them go
Hello,
I am looking to had some more power to squid. I have seen two different
types of configurations to do this:
1. Adding workers directive equal to the number of cpus. Then adding a
special wrapper around the AUFS disk cache so that the correct worker can
only access the correct cache. Yes, I
I am currently using Squid 3.1 that comes packages in RHEL 6. I have this
line in my config:
http_port 80 intercept
I have a split horizon dns. This means if you lookup any address for my
domain from the internet you get the address of the squid proxy server.
However if you lookup the same nam
On 17/06/2015 10:11 p.m., Horváth Szabolcs wrote:
> Hello!
>
> We're having serious problems with a squid proxy server.
>
> The good news is the problem can be reproduced at any time in our production
> squid system.
>
> Environment:
> - CentOS release 6.5 (Final) with Linux kernel 2.6.32-431.
On 18/06/2015 8:53 a.m., Michael Pelletier wrote:
> Hello,
>
> I am looking to had some more power to squid. I have seen two different
> types of configurations to do this:
>
> 1. Adding workers directive equal to the number of cpus. Then adding a
> special wrapper around the AUFS disk cache so t
On 18/06/2015 9:23 a.m., Jeff Scarborough wrote:
> I am currently using Squid 3.1 that comes packages in RHEL 6. I have this
> line in my config:
> http_port 80 intercept
>
> I have a split horizon dns. This means if you lookup any address for my
> domain from the internet you get the address
On 17/06/2015 6:52 p.m., Jason Haar wrote:
> On 15/06/15 11:58, Amos Jeffries wrote:
>> Ensure that you are using the very latest Squid version to avoid
>> problems with unsupported TLS mechanisms. The latest Squid will also
>> automatically splice if its determined that the TLS connection cannot b
Which one would be good for capacity\load? I have a very, very large
environment. I have 220,000 users on 8 Gig to the INTERNET. I am running a
load balancer, ipvsadm (Direct Routing) with 20 proxies behind it. I am
interested in handling load.
Michael
On Wed, Jun 17, 2015 at 9:31 PM, Amos Jeffri
12 matches
Mail list logo
