On Sat, 11 Sep 1999, Matthew Hawkins wrote: > process. Oh, and squid also groks HTTP/1.1. rproxy is simply a > proof-of-concept implementation and technically isn't meant to grok > anything ;)
squid mostly groks http/1.1, APT can cause it to puke out on sometimes - but it's rare > > wwoffle and apache-proxy have problems, squid and many others do not, I > > suggest you strace the http method process and see what system call is > > causing it to print that error.. > > Unfortunately I am not fast enough to find out the pid of the http > method process and strace it before the problem occurs. As you claim > apt is working within spec, I'll try the reverse solution and work with Use strace -o /tmp/apt -ff apt-get [...] that will capture the http session's strace for you to examine. You should be able to determine what is happening quite quickly from that. Jason
