[squid-users] Introducing Charcoal - Centralised URL Filter for squid

[Nishant Sharma]

On 17 June 2017 11:17:38 PM IST, Amos Jeffries <squid3 at treenet.co.nz> wrote:

>That would mean making Squid aware of the internal workings of the 
>helper. Namely that it uses connections to a specific server, port and 
>which transport. One of the major points of flexibility with helpers is
>
>that this kind of thing is kept completely separate from Squid.

Re-reading my mail made me realise that it conveyed that helper architecture of squid be modified,  instead I wanted to say that we can modify the architecture of our helper, where it internally manages its own children which may speed-up the URL rewrite process.

>The URL-rewrite API being used by charcoal has the purpose of altering 
>the URI which Squid fetches content for a client from. Doing access 
>control through it instead of the access control API (external ACL 
>helper) is kind of borked from the start.

I agree, external ACL helper will also allow to have access to  additional information like user-agent, reply content-type etc. to have more granular control.

Regards,
Nishant
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.