Hello Michael,
That depends on what you want to filter out.
If you do it in client_side.c you still have an opportunity to use
squids internal error handling to issue a error page.
If you want to sniff out the stream you can do it in http.c, but when
you see something you don't like the only way I've found to interrupt
and reset the browser is my issuing a java redirect to an errorpage.
If you want to intercept things even before all that, I think you want
to do it in comm.c but I've never had a need to look at things that
early on.
-- Joe
Quoting Michael Kaplan <michael.a.kaplan_at_gmail.com>:
> I think my original email may have been unclear, so let met restate.
>
> Within Squid, I want to add a module that filters the traffic entering
> Squid from the internal network sitting behind the Squid proxy
> dedicated machine. Preferably this module would examine the traffic
> before Squid takes much action, allowing my module to choose whether or
> not to pass on the packet further in Squid for processing. Yes, I know
> this could be done outside of Squid, but I have reasons for doing this
> within Squid. Where within squid would be the ideal place to intercept
> these incoming packets?
>
> Thank You
>
> Mike
Received on Tue Jul 15 2008 - 16:48:33 MDT
This archive was generated by hypermail 2.2.0 : Wed Jul 16 2008 - 12:00:06 MDT