Intergrate McAfee Web Gateway with Squid

[VietDuc19]

Hi everyone!

I am configuring McAfee Web Gateway with Squid. Here is my diagram:

- Squid Cache: Version 4.8

- 3 McAfee Web Gateway Servers: Version 7.8.2.14

Our PC will point to IP address of squid to access Internet and squid will talk to Web Gateway via next-hop proxy by using cache_peer directive of squid.

I want to load-balance between 3 McAfee Web Gateway Servers when communicating with squid by using round-robin peer.

Here is my squid configuration file to do that:

#Round-Robin Cache_Peer With Mode Parent McAfee Web Gateway
cache_peer IP_MWG_Server_1 parent 80 0 name=mcwg2 no-query weighted-round-robin weight=2
cache_peer IP_MWG_Server_2 parent 80 0 name=mcwg3 no-query weighted-round-robin weight=1
cache_peer IP_MWG_Server_3 parent 80 0 name=mcwg1 no-query default
prefer_direct off
nonhierarchical_direct off

However, when I check access.log of squid, I see the following error from multiple IP client:

1574238106.334 0 IP_Client NONE/000 0 NONE error:transaction-end-before-headers - HIER_NONE/- -
1574238106.334 0 IP_Client NONE/000 0 NONE error:transaction-end-before-headers - HIER_NONE/- -
1574238106.334 0 IP_Client NONE/000 0 NONE error:transaction-end-before-headers - HIER_NONE/- -
1574238106.334 0 IP_Client NONE/000 0 NONE error:transaction-end-before-headers - HIER_NONE/- -
1574238106.335 0 IP_Client NONE/000 0 NONE error:transaction-end-before-headers - HIER_NONE/- -
1574238107.335 0 IP_Client NONE/000 0 NONE error:transaction-end-before-headers - HIER_NONE/- -

I tried to tcpdump and really don't know why there are no headers on request. Anyone can help me to troubleshoot this error or what exactly meaning of this error?

Thank you so much for your help.

[swilkens1]

 Hi @VietDuc19 , this seems more like an error reported on the Squid side. Does this mean that the client request was sent without headers from PC to Squid? Or no headers were sent back in the reply from MWG to Squid?

[VietDuc19]

Hi @swilkens1: I tried to capture packet on squid and saw that: client sent request without headers to squid. This happened on squid version 4.8 but when I tried on squid version 3.5, this warning didn't appear any more. 

[swilkens1 · Accepted solution]

I understand. Unfortunately, I do not know any specifics about those two Squid versions. Typically we focus on the Web Gateway and solving issues with the Web Gateway here.

Right now there is nothing indicating that the Web Gateway is causing the issue, since you notice problems before traffic even gets sent to MWG.

Perhaps you would find better success if you posted this question on a Squid forum?

[VietDuc19]

I totally agree with you. I will post my question to squid forum and find the solution for my problem. Thanks you so much for your support on my topic.