On 24/02/19 9:55 am, Hernan Saltiel wrote:
> Hi,
> I'm trying to use a Squid 3.1.20 to update several Windows Clientes
> (some are Vista, some are 7, some are 10).
> We're using NTLM authentication, and some groups (some users can use
> full internet, some can only on some sites) and this i
I am testing intermediate certificates and I have just created a key and
certificate files.
The http line for ssl bump is:
http_port 23128 ssl-bump generate-host-certificates=on
dynamic_cert_mem_cache_size=16MB cert=/etc/squid/ssl_cert/cert.pem
key=/etc/squid/ssl_cert/key.pem
While running squi
What would be the reason to replace haproxy eactly?
Eliezer
Eliezer Croitoru
Linux System Administrator
Mobile: +972-5-28704261
Email: elie...@ngtech.co.il
-Original Message-
From: squid-users On Behalf Of
David Touzeau
Sent: Saturday, February 23, 2019 18:31
To: squid-users@list
On 2/23/19 10:17 AM, Amos Jeffries wrote:
> On 24/02/19 5:33 am, David Touzeau wrote:
>> http.cc(982) haveParsedReplyHeaders: decided: do not cache but share
>> because the entry has been released; HTTP status 200
>> What “but share because the entry has been released” event means ?
> 'do not cac
Just add before the line:
http_access deny !auth
a localnet allow windows update rule.
It should be something like:
## Start of config snippet
acl windows_updates dstdomain "/etc/squid3/windows_update"
acl src locanet 192.168.42.0/24
http_access allow localnet windows_updates
http_access deny
Hi,
I'm trying to use a Squid 3.1.20 to update several Windows Clientes
(some are Vista, some are 7, some are 10).
We're using NTLM authentication, and some groups (some users can use
full internet, some can only on some sites) and this is working fine.
The issue arises when trying to u
The next tool might help you to understand the status of the open
connections.
If the socket is being closed( I think Windows Server 2016 is a very good
OS...).
https://www.nirsoft.net/utils/cports.html
There is a possibility that some OS TCP limit is being reached and there for
the socket closure
I can think of a way to try and "amend" on an error in the next websocket
connection automatically.
I believe that using an ICAP service or eCAP module that is connected to an
external acl helper you can see if specific requests for specific domains
are trying to use websockets.
Technically the bas
On 24/02/19 5:33 am, David Touzeau wrote:
> Hi
>
> I’m trying to store in cache an Internet file
>
>
> Run the squid in debug mode says:
>
> http.cc(982) haveParsedReplyHeaders: decided: do not cache but share
> because the entry has been released; HTTP status 200
>
> What “but share because t
On 24/02/19 5:30 am, David Touzeau wrote:
>
> Currently we are working on Kerberos with Active Directory with Ha-proxy
> that
> sends requests to squid using proxy_protocol.
> Everything works great but we want to replace the ha-proxy with a squid.
> In fact, we want to the squid client send the
Hi
I'm trying to store in cache an Internet file
Run the squid in debug mode says:
http.cc(982) haveParsedReplyHeaders: decided: do not cache but share because
the entry has been released; HTTP status 200
What "but share because the entry has been released" event means ?
Currently we are working on Kerberos with Active Directory with Ha-proxy
that
sends requests to squid using proxy_protocol.
Everything works great but we want to replace the ha-proxy with a squid.
In fact, we want to the squid client send the credentials information to a
squid parent in order to
12 matches
Mail list logo
