[squid-users] Migration from squid 3.1.20 to 3.4.8

[Amos Jeffries]

On 10/06/2015 9:39 p.m., Diercks, Frank (VRZ Koblenz) wrote:
> Hallo squid-users,
> 
> i migrated our Proxy from 3.1.20 to 3.4.8. Here are the changes I made:
> 
> I commented out:
> #acl manager proto cache_object
> #acl localhost src 127.0.0.1/32 ::1
> #acl to_localhost dst 127.0.0.0/8 0.0.0.0/32 ::1
> 
> And added the following entry:
> http_port xxx.xxx.xxx.xxx.:3129 intercept (port 3128 was already without "intercept" configured).
> 
> Everything runs well, except an application which sends data via html to our internetserver.
> 
> The first entry is from squid 3.1.20, which runs without problems:
> . .. TCP_MISS/200 317 POST http://xxx.xxx.xxx.xxx/SWIS-Web/TLSReceiver - DIRECT/xxx.xxx.xxx.xxx -
> 
> The second entry is from squid 3.4.8:
> ... TAG_NONE/400 3585 POST /SWIS-Web/TLSReceiver - HIER_NONE/- text/html
> 
> As you can see, squid 3.4.8 doesn't log the http-part. I have no idea why. The entries from cache.log and access.log are clean.
> Every hint is welcome.

Looks like it is being intercepted. But does it contain a Host: header?

Try "debug_options 11,2" to see in cache.log what the messages are.

Amos