On 3/10/19 5:55 pm, Erick Perez - Quadrian Enterprises wrote:
> On Wed, Oct 2, 2019 at 10:47 PM Erick Perez - Quadrian Enterprises wrote:
>>
>> Hi, maybe somebody here experienced the same issues while working with
>> WPAD files.
>>
>> I have a working Centos 7.6/SQUID v4.8 that works as expected.
On Wed, Oct 2, 2019 at 10:47 PM Erick Perez - Quadrian Enterprises
wrote:
>
> Hi, maybe somebody here experienced the same issues while working with
> WPAD files.
>
> I have a working Centos 7.6/SQUID v4.8 that works as expected.
> It works as long as I manually configure the proxy in the network
Hi, maybe somebody here experienced the same issues while working with
WPAD files.
I have a working Centos 7.6/SQUID v4.8 that works as expected.
It works as long as I manually configure the proxy in the network
settings of each workstation (windows) firefox browser 69.0.1 (64bit)
and the same beh
On 10/2/19 2:51 PM, johnr wrote:
> I was wondering how / if it was possible to annotate a request from
> within an ICAP service.
A long-term solution requires two steps:
1. Modify your ICAP service to return a custom ICAP response header.
2. Modify Squid to treat ICAP response headers (with na
Hi,
I was wondering how / if it was possible to annotate a request (basically,
set a note/tag similarly to how the external ACL can) from within an ICAP
service.
My use-case is that I would like to add a note with information about the
request that is then available for use within external helper
On 10/2/19 10:50 AM, Matus UHLAR - fantomas wrote:
> On 02.10.19 16:22, Matus UHLAR - fantomas wrote:
>> http://bugs.squid-cache.org/show_bug.cgi?id=4977
> OK, now I've got 1.7G pcap, 2.8M access.log (22k requests) and cache.log
> saying when did the problem appear.
> Any idea what to search for?
On 02.10.19 16:22, Matus UHLAR - fantomas wrote:
related to http://bugs.squid-cache.org/show_bug.cgi?id=4977
(In reply to Matus UHLAR - fantomas from comment #12)
> We notice the same problem after few minutes running squid 4.6 (debian 10,
> x86_64):
>
> 2019/10/02 05:00:53 kid1| asser
Hello,
related to http://bugs.squid-cache.org/show_bug.cgi?id=4977
(In reply to Matus UHLAR - fantomas from comment #12)
> We notice the same problem after few minutes running squid 4.6 (debian 10,
> x86_64):
>
> 2019/10/02 05:00:53 kid1| assertion failed: stmem.cc:98: "lowestOffs
On 10/2/19 7:49 AM, Matus UHLAR - fantomas wrote:
> Hello,
>
> We have recently upgraded debian 9/squid 3.5.23 to debian 10/squid 4.6
>
> Since then, we see many errors like these:
>
> 1569967208.535 3651 192.168.aa.bbb TCP_TUNNEL_ABORTED/200 7200 CONNECT
> arc.msn.com:443 - HIER_DIRECT/52.229
Hello,
We have recently upgraded debian 9/squid 3.5.23 to debian 10/squid 4.6
Since then, we see many errors like these:
1569967208.535 3651 192.168.aa.bbb TCP_TUNNEL_ABORTED/200 7200 CONNECT
arc.msn.com:443 - HIER_DIRECT/52.229.207.60 -
1569967212.488 170668 192.168.cc.ddd TCP_TUNNEL_ABORTE
>... considering security and filtering ...<
Regarding filtering, you might consider DNS-based filtering.
I did special developments in this area, i.e. for "Parental Control" and
ad/tracker-blocking.
"TLS everywhere" I consider a special trick of goggle, to protect their
ads/trackers from being ea
11 matches
Mail list logo