HTTP Anti-Virus Proxy
http://havp.hege.li/forum/

HAVP: Server is down Could not read headers
http://havp.hege.li/forum/viewtopic.php?f=3&t=469
Page 1 of 1

Author:  Fantomasperu [ 21 Jul 2009 18:20 ]
Post subject:  HAVP: Server is down Could not read headers

when trying to open the url http://www.cal.org.pe I get the error,HAVP: Server is down Could not read headers.

EFW not ping the ip of this url, but from outside the EFW if I can enter.


some solutions to this problem. havp-0.89-2.endian7 with squid-2.6.STABLE18-5.endian6

Author:  karesmakro [ 23 Jul 2009 13:45 ]
Post subject:  Re: HAVP: Server is down Could not read headers

Hi Fantomasperu!

I have no problem to open this page! Currently I use HAVP-0.91 and squid/2.7.STABLE3.
My experience is, mostly this is a problem of squid configuration. Sorry, I don't know, how EFW handles this requests and how EFW implements havp with squid proxy.

regards

Author:  Harri [ 11 Nov 2010 16:48 ]
Post subject:  Re: HAVP: Server is down Could not read headers

I get this problem without squid, just using transparent havp. I can reproduce it using

http://macuser.de/

To reproduce click on the button labeled "Anmeldung" at the top edge of this page. If I do a reload then the problem is gone. If I restart Firefox and try again then the problem is back.

Havp is version 0.91 as found in Debian unstable. Firefox is version 3.6.12. Both run on Debian sid amd64 (on different hosts). The firewall to do the redirection runs OpenBSD 4.3.

It would be very nice if we could find a solution for this. I would be glad to help.

Author:  karesmakro [ 11 Nov 2010 20:34 ]
Post subject:  Re: HAVP: Server is down Could not read headers

Hi Harri!

Can double check you network configuration and how the client resolves dns?
resolve.conf, or using bind
Are there more sites, which are affected by the server down message?

I had no problem to open this page! What about configuring havp with a fix port, not transparently, are you also get this message?
And please check the havp error.log for uncommon entries.

regards

Author:  Harri [ 12 Nov 2010 10:28 ]
Post subject:  Re: HAVP: Server is down Could not read headers

karesmakro wrote:
Can double check you network configuration and how the client resolves dns?
resolve.conf, or using bind

I checked. http client and havp proxy got the same resolv.conf, but for looking up external hosts this shouldn't matter, anyway. Even if 2 hosts ask the same DNServer, they might get different answers.

I've got a 300+ hosts local network, all using the same bind9 servers. Of course there might be a misconfiguration, but for the hosts without redirection to havp there is no such problem. I would say its more likely to be a problem with havp or the transparent redirection than with bind9.

Author:  Harri [ 12 Nov 2010 11:07 ]
Post subject:  Re: HAVP: Server is down Could not read headers

karesmakro wrote:
I had no problem to open this page! What about configuring havp with a fix port, not transparently, are you also get this message?
And please check the havp error.log for uncommon entries.

I got tons of error messages "Could not read server header" in the log file for http://www.bluray-disc.de/, but please note that its "server header". The web page looks fine.

If I disable transparent mode, configure the proxy in firefox instead, and restart both, then I still get the "could not read headers" for macuser.de --> Anmeldung. Its not a problem with transparent mode, afaics.

Author:  Harri [ 08 Dec 2010 17:46 ]
Post subject:  Re: HAVP: Server is down Could not read headers

I checked network communication using tcpdump and wireshark. Using havp it seems that the http server gets confused and hangs up. On a reload its working. Without havp it is working fine right from the start.

If somebody is interested I can forward the tcpdump files for similar sessions with and without havp.

Author:  karesmakro [ 19 Dec 2010 20:08 ]
Post subject:  Re: HAVP: Server is down Could not read headers

A little bit late ...
I have the same problem with "Could not read server header" on some machines, but there was no need, to reload. The strange is, that it affects different from server to server.
I searched long time for the cause, because I have also server configurations, where this problem has never occurred. It is partly the same configuration, but newer environments and partly different firewalls.

At this moment, I'm still puzzled ... :(
If I find an answer, I'll post it here.

regards

Page 1 of 1 All times are UTC + 2 hours [ DST ]
Powered by phpBB® Forum Software © phpBB Group
https://www.phpbb.com/