Hi all,
https://www.spinics.net/lists/squid/msg90523.html
As mentioned in the above URL, I would like to use "SSL Bump with HTTP
Cache Peer Parent" as well.
However, still seems not be supported like the following.
- FwdState.cc (in squid-4.8 which is currect stable version)
825 FwdState::c
On 14/07/19 3:17 pm, TarotApprentice wrote:
> Thanks. Debian still have 4.6. I’ll raise a bug for Debian in the hope they
> will get them into Buster and Stretch via their backports repos. They seem to
> ignore emails, even to the maintainer group.
>
Already packaged and awaiting Luigis' test a
Thanks. Debian still have 4.6. I’ll raise a bug for Debian in the hope they
will get them into Buster and Stretch via their backports repos. They seem to
ignore emails, even to the maintainer group.
> On 14 Jul 2019, at 12:24 pm, Amos Jeffries wrote:
>
>> On 14/07/19 11:04 am, TarotApprentice
On 14/07/19 11:04 am, TarotApprentice wrote:
> On the Squid-Announce list there were advisories 2019:1, 2, 3, 5 and 6. Was
> there a 2019:4 that was missed?
>
Yes and no. There is a :4 issue. But the fix turned out to be
incomplete so did not make it into this release.
Amos
___
On the Squid-Announce list there were advisories 2019:1, 2, 3, 5 and 6. Was
there a 2019:4 that was missed?
MarkJ
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users
The Squid HTTP Proxy team is very pleased to announce the availability
of the Squid-4.8 release!
This release is a security release resolving several issues found in
the prior Squid releases.
The major changes to be aware of:
* SQUID-2019:1 Denial of Service issue in cachemgr.cgi
(CVE-201
__
Squid Proxy Cache Security Update Advisory SQUID-2019:5
__
Advisory ID:SQUID-2019:5
Date: July 12, 2019
Summary:Heap Overflow is
__
Squid Proxy Cache Security Update Advisory SQUID-2019:6
__
Advisory ID:SQUID-2019:6
Date: July 12, 2019
Summary:Multiple Cross-S
__
Squid Proxy Cache Security Update Advisory SQUID-2019:3
__
Advisory ID:SQUID-2019:3
Date: July 12, 2019
Summary:Denial of Servic
__
Squid Proxy Cache Security Update Advisory SQUID-2019:2
__
Advisory ID:SQUID-2019:2
Date: July 12, 2019
Summary:Denial of Servic
__
Squid Proxy Cache Security Update Advisory SQUID-2019:1
__
Advisory ID:SQUID-2019:1
Date: July 12, 2019
Summary:Denial of Servic
On 7/13/19 7:37 AM, Amos Jeffries wrote:
> On 13/07/19 9:55 pm, --Ahmad-- wrote:
>> i want it when squid access / contact with 1.2.3.4
> Use "dst" ACL for destination IP's.
> However, requests are generated before sending. Squid does not know
> which IP will *in future* be used to deliver the req
On 13/07/19 9:55 pm, --Ahmad-- wrote:
>
>
> i want it when squid access / contact with 1.2.3.4
>
>
Use "dst" ACL for destination IP's.
However, requests are generated before sending. Squid does not know
which IP will *in future* be used to deliver the request. So this is
unlikely to work prop
i want it when squid access / contact with 1.2.3.4
Thanks
> On 13 Jul 2019, at 12:36, Matus UHLAR - fantomas wrote:
>
> when accessing 1.2.3.4 or whn your client is 1.2.3.4?
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://
On 13.07.19 12:20, --Ahmad-- wrote:
say i have a set of rules to block some certain types of headers as below :
header_access Pragma deny all
header_access Keep-Alive deny all
but i want those above two headers allowed when accessing ip 1.2.3.4
is my config below is correct ? i tested but di
hello folks .
say i have a set of rules to block some certain types of headers as below :
header_access Pragma deny all
header_access Keep-Alive deny all
but i want those above two headers allowed when accessing ip 1.2.3.4
is my config below is correct ? i tested but didn’t work
acl allowip
16 matches
Mail list logo
