On 08/13/2015 10:31 PM, Amos Jeffries wrote:
> AFAICS it
> is the backend AV library only scanning disk objects that causes the
> whole issue. Otherwise the eCAP could be much, much faster.
The situation is more nuanced: eCAP supports asynchronous adapters. It
is possible to write a ClamAV adapter
On 2015-08-13 10:18 am, Amos Jeffries wrote:
On 14/08/2015 2:40 a.m., Julianne Bielski wrote:
But does this mean that ECDHE isn't supported by Squid?
Correct. ECDHE is not supported by 3.5 and older.
EECDHE and ECDHE are coming in Squid-4.
If you really need it you are welcome to download
Quoting Antony Stone :
On Friday 14 August 2015 at 14:10:54, Arjen van der Meer wrote:
Dear Antony (and Amos),
Thanks again for your replies. This answers my question, however I had
hoped for a solution that would make /wordpress invisible from the
outside.
In that case remove the ^/wordpre
On Friday 14 August 2015 at 14:10:54, Arjen van der Meer wrote:
> Dear Antony (and Amos),
>
> Thanks again for your replies. This answers my question, however I had
> hoped for a solution that would make /wordpress invisible from the
> outside.
In that case remove the ^/wordpress ACL from your s
Hello,
I am trying to write an ICAP module for the C ICAP server. My purpose is to
rewrite HTTP responses which flow through my Squid proxy. However, the
documentation to write such service modules and build them doesn't seem
very good. Does anyone have pointers to some good tutorial online or any
Dear Antony (and Amos),
Thanks again for your replies. This answers my question, however I had hoped
for a solution that would make /wordpress invisible from the outside.
I will reinstate the rewriter that did the before but exposes the /wordpress
in the URL.
Kind regards,
Arjen.
Message
On Friday 14 August 2015 at 12:37:49, Antony Stone wrote:
> On Friday 14 August 2015 at 10:57:52, Arjen van der Meer wrote:
> > Good morning Amos,
> >
> > And thanks for your reply. But I think this is what I already have
> > configured, unless you notice errors in the following configuration:
>
On Friday 14 August 2015 at 10:57:52, Arjen van der Meer wrote:
> Good morning Amos,
>
> And thanks for your reply. But I think this is what I already have
> configured, unless you notice errors in the following configuration:
> acl wordpress urlpath_regex ^/wordpress
The above matches any URL
Good morning Amos,
And thanks for your reply. But I think this is what I already have configured,
unless you notice errors in the following configuration:
acl wordpress urlpath_regex ^/wordpress
cache_peer 192.168.1.150 parent 80 0 no-query originserver name=ubuntu
cache_peer_access ubuntu deny
