Just talked to the debian guys. They won't upgrade squid to 3.5 in
debian jessi. It's also hard for me, to implement unstable components
in a productive system.
But the debian guys told me, that they will build own patches for
3.4.8 to fix critical problems if you report them properly to
https://
Hi
so I have this in place now
This works well for delaying YAY
#
# Delay Pools
# http://wiki.squid-cache.org/Features/DelayPools
#
http://www.serverwatch.com/tutorials/article.php/3357241/Reining-in-Bandwidth-With-Squid-Proxying.htm
delay_pools 1
delay_class 1 1
# 10Mb/s fille rate , 20Mb/s r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
This is most probably client certificate error. IM or something. You can
ignore it if users not compliances.
18.01.16 3:13, Roman Gelfand пишет:
> I am not sure where I am going wrong here...
>
>
> ssl bump certificate
> openssl req -new -newkey r
I am not sure where I am going wrong here...
ssl bump certificate
openssl req -new -newkey rsa:2048 -sha256 -days 365 -nodes -x509 -keyout
squidCA.pem -out squidCA.pem
The der certificate was generated and deployed on client computer trusted
root
openssl x509 -in squidCA.pem -outform DER -out s
On 17/01/16 06:16, xxiao8 wrote:
> Basically I'm trying to see how to get the http-header info from a
> bumped ssl connection and use them directly inside
> squid.conf(including external acl), otherwise icap/ecap is unavoidable
> for bumped ssl http header analysis.
You must have done it wrong. Fi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
No.
18.01.16 0:56, Roman Gelfand пишет:
> I am getting an error, below, in a cache.log. How can I identify the
> request associated with this error? It doesn't appear to be an issue with
> client-to-proxy. It seems like a problem with proxy-to-
I am getting an error, below, in a cache.log. How can I identify the
request associated with this error? It doesn't appear to be an issue with
client-to-proxy. It seems like a problem with proxy-to-remote_server.
Error negotiating SSL on FD 43: error:14090086:SSL
routines:SSL3_GET_SERVER_CERTIF
On Sunday 17 January 2016 at 08:55:56, behrad eslami wrote:
> Hi
> Some part of our traffic is asymmatric (send and receive had different
> route)Is squid cat work on one direct (only on receive)?
If you're asking whether Squid will cache and/or proxy replies from webservers
where it hasn't seen
