Hi,
Sorry I am asking this question again. I am trying to setup HTTPS
proxy using ssl-bump. I have followed
steps mentioned in:
http://wiki.squid-cache.org/ConfigExamples/Intercept/SslBumpExplicit
Following are Squid setup details:
Squid Cache: Version 3.5.12
Service Name: squid
Ubuntu linux
On 02/23/2017 12:02 PM, sebastien.boulia...@cpu.ca wrote:
> Does it has changes in the configuration from Squid 3.5.20 vs 3.5.24 ?
I see one configuration change clearly identified in ChangeLog:
> - TLS: Make key= before cert= an error instead of quietly hiding the issue
There may be more -- I
Hi Eli,
It stops working like when I tried to access a website, I got a error
connection reset by peer.
I will try to add the cache deny all at the end of the file.
Thanks,
Sébastien.
-Message d'origine-
De : Eliezer Croitoru [mailto:elie...@ngtech.co.il]
Envoyé : 23 février 2017
What do you mean by stopped working?
100% CPU?
If so please try to add as the last line of squid:
cache deny all
and see if it happens again.
All The Bests,
Eliezer
http://ngtech.co.il/lmgtfy/
Linux System Administrator
Mobile: +972-5-28704261
Email: elie...@ngtech.co.il
From:
Hi all,
Does it has changes in the configuration from Squid 3.5.20 vs 3.5.24 ?
My Squid stop working for no reason BUT i dont know why. To fix that, I have to
restart the Squid process.
Do you have any idea how to know what it causes that ?
Thanks you for your answer.
Sébastien
On 24/02/2017 12:23 a.m., Imaginovskiy wrote:
> Hi All,
>
> I'm in the process of upgrading some clients to the latest squid proxy
> version. Coming from version 3.5 I used to specify backends in squid.conf as
> follows;
>
> cache_peer site1.domain.com parent 443 0 no-query originserver
>
Hi All,
I'm in the process of upgrading some clients to the latest squid proxy
version. Coming from version 3.5 I used to specify backends in squid.conf as
follows;
cache_peer site1.domain.com parent 443 0 no-query originserver
name=server_site1 ssl proxy-only front-end-https=on login=PASS
Hello list,
we want to filter with squidGuard and decide based on the username,
identified with ident. In the bug tracker I found the old entry 2655
with this bug, which had been marked as fixed, but is still present in
3.5.24. I have recently reopened that bug with some info about our
szenario.
