I'm examining POST messages, primarily the mutlipart/formdata section. I
am looking at the hp->buf within processHttpRequest function in
client_side.cc, but it did not appear that this structure contained the
whole post messages - only the beginning of the http header, and not
some of the additional headers that appeared lower in the message. I am
trying to find a way to get more the header information. Potentially I
may not want Squid to forward the POST on to the destination.
Mike
Henrik Nordstrom wrote:
On tis, 2008-07-15 at 12:11 -0400, Michael Kaplan wrote:
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.
Hmm.. Squid does not operate on packets. Squid is an application ontop
of TCP/IP. When Squid sees the data it has already been processed by the
TCP/IP stack, serialized into a TCP stream and fed to Squid as a
sequence of octets from the TCP stream.
At that point it's not an option to not further process the data within
Squid.
What is your actual goal with this?
Regards
Henrik
