Comment 28 for bug 474475

I'm not sure this will help, but I did some tcpdumps between tinyproxy and squid responses (on -i lo). I'm not sure how to interpret them, so I'll attach them here, maybe somebody can make sense of these.

As far as I can tell, when using squid, the HTTP OK response gets back correctly, but not with tinyproxy. If you take a look with wireshark, frames 6-18 in with-squid.cap, everything looks normal, there are a couple of packets and that's it. In with-tinyproxy.cap however, there are a lot more packets (6-27) and there's no actual 'HTTP/1.0 OK'.

The tinyproxy response differs too, header-wise. I'm not saying that tinyproxy's doing anything wrong (because when using tinyproxy without dansguardian, the above pages load just fine), but maybe dansguardian gets confused by tinyproxy's response, or something...

I'm also getting this in dansguardian's access.log when using tinyproxy:

2010.4.13 0:31:56 - 172.16.21.6 http://old-releases.ubuntu.com/releases/ GET 0 0 1 200 text/html -

and this with squid:

2010.4.13 0:57:19 - 172.16.21.6 http://old-releases.ubuntu.com/releases/ GET 4075 -20 1 200 text/html -