Hey Martin,
I was wondering if you had the chance of trying to enforce some QOS
policy on the OS level?
Also what OS and distribution are you using?
Eliezer
On 17/02/2016 03:37, Hery Martin wrote:
Hello everybody:
Since a few months ago I'm using squid to provide a solution as small
Hey djch Thanks for your quick reply...
Anyway, I know that delay pools are implemented at software layer, but
maybe the error was just a simple mistake porting the old squid 2 project.
Even when these days we have tools to do this more efficiently like TC-CBQ,
in environments where squid works
It's been a while since I've looked at this—because the software we use to
generate our squid.conf just works around now—but we found that Squid 3
would only enforce exactly half the configured rate on HTTP requests but
enforce the full rate on HTTPS requests.
So we now make two delay pools for
Hello everybody:
Since a few months ago I'm using squid to provide a solution as small
business proxy in the network of my work place.
I'm from Cuba, in our country the Internet is a very limited resource. I
have only one link of 2Mbps to share with 20 ~ 25 users (even with my
network have more
Hi All,
Currently i have Squid 3.5.12 setup with LDAP Authentication and with
groups. If a certain user is apart of a certain group they can access sites
that are listed in the allowed list, otherwise access is denied for all
other sites.
I have a new requirement to allow all LDAP authenticated
Hi all,
http://imgur.com/PI1PRlB
Can it be fixed with Squid ? If yes, how ?
Thanks you very much for your answer.
Sébastien Boulianne
Administrateur réseau & système / Network & System Administrator (Windows &
Linux).
Gestion des infrastructures / Infrastructure Management.
CCNA / CompTIA
Before digging into the details of the issue, can you supply the OS details?
What OS are you using? What distribution?
32 or 64 bit?
can you also add the output of "squid -v" for both 3.5.14 and 3.5.13 ?
Thanks,
Eliezer
On 16/02/2016 16:32, Jester Purtteman wrote:
Greetings Squid users,
With
On 17/02/2016 3:11 a.m., luc...@dds.nl wrote:
> Hi List,
>
> I am using Squid 3.1.23 as a reverse proxy. Client authentication to
> backend servers is mandatory. All backend servers use client certificate
> based authentication which I configure as follows:
> cache_peer (...) ssl
Greetings Squid users,
With 3.5.14 out and activating CFLAGS, I am getting into trouble. Funny
too, I spent a lot of time wondering why it wasn't adding CFLAGS in earlier
builds. In any event, I have a 3.5.13 instance configured as follows:
./configure --prefix=/usr
Hi List,
I am using Squid 3.1.23 as a reverse proxy. Client authentication to
backend servers is mandatory. All backend servers use client certificate
based authentication which I configure as follows:
cache_peer (...) ssl sslcert=/etc/squid/client-certs/client-cert.pem
(...)
The .pem file is
__
Squid Proxy Cache Security Update Advisory SQUID-2016:1
__
Advisory ID:SQUID-2016:1
Date: February 16, 2016
Summary:Remote Denial
The Squid HTTP Proxy team is very pleased to announce the availability
of the Squid-3.5.14 release!
This release is a security release resolving one major vulnerability and
several other bugs found in the prior Squid releases.
The major changes to be aware of:
* SQUID-2016:1 - Remote Denial
I had to try overwriting the directives in the squid.conf since it was
the quickest and most obvious solution to me.
I can assure you, it works.
On 15.02.2016 10:59, Amos Jeffries wrote:
> On 15/02/2016 10:51 p.m., Stefan Hölzle wrote:
>> For a quick fix, I defined the two directives in my
okay now i have this
acl step1 at_step SslBump1
ssl_bump peek step1
ssl_bump splice all
but all https connections is TCP_TUNNEL/200
i need only sni requests that cant be bumped to be TCP_TUNNEL/200 !!!
and the other request must bumped and decrypt !!
--
View this message in context:
14 matches
Mail list logo
