HTTP Anti-Virus Proxy :: View topic - [Solved] Could not send header to browser

What's your problem? You open more then one thread about one problem, give no response about my suggestions. To this day, i don't know about your squid version.
How can anybody help you? What dou you expect?

Help was offered to you. See faq's. Still, there is any problem in your squid configuration and no log messages to this day ...

Please forgive me, but people spend time to help you, but no cooperation ..

Edit :arrow:

found squid version in your blog

Yes. As i remember, i had the same problem long time ago ...
I'm happy, i could help you!

Can you please change subject to solved?

greetings, Kare :wink:

That's right. I've one debian server with squid - havp -clamv and one IPCop in front of my debian server with clamav + havp too. The one on my debian server is for experimental and to prepare configuration for companies.
Why this question?

greetings, Kare :wink:

Author:	badm4n [ 10 Dec 2008 09:00 ]
Post subject:	[Solved] Could not send header to browser
09/12/2008 08:49:56 (192.168.77.77) Could not send header to browser 09/12/2008 08:49:56 (192.168.77.77) Could not send header to browser 09/12/2008 09:06:19 (192.168.77.77) Could not send header to browser 09/12/2008 11:16:43 (192.168.77.77) Could not read browser body 09/12/2008 13:51:19 (192.168.77.77) Could not send header to browser 09/12/2008 13:52:10 (192.168.222.100) Could not read server header (192.168.77.77/mail.pulse.com.au:80) 09/12/2008 13:53:05 (192.168.77.77) Could not send header to browser 09/12/2008 16:01:03 (192.168.77.77) Could not send header to browser 09/12/2008 16:55:58 (192.168.77.77) Could not send header to browser 10/12/2008 12:35:32 (192.168.77.77) Could not send header to browser 10/12/2008 12:35:54 (192.168.222.100) Could not read server header (192.168.77.77/mail.pulse.com.au:80) 10/12/2008 12:40:33 (192.168.222.100) Could not read server header (192.168.77.77/mail.pulse.com.au:80) 10/12/2008 12:40:33 (192.168.222.100) Could not read server header (192.168.77.77/mail.pulse.com.au:80) 10/12/2008 12:40:44 (192.168.77.77) Could not send header to browser 10/12/2008 12:41:04 (192.168.222.100) Could not read server header (192.168.77.77/mail.pulse.com.au:80) 10/12/2008 12:45:33 (192.168.77.77) Could not send header to browser 10/12/2008 12:46:02 (192.168.222.100) Could not read server header (192.168.77.77/mail.pulse.com.au:80) 10/12/2008 12:50:05 (192.168.222.100) Could not read server header (192.168.77.77/mail.pulse.com.au:80) 10/12/2008 12:50:19 (192.168.222.100) Could not read server header (192.168.77.77/mail.pulse.com.au:80) 10/12/2008 12:50:19 (192.168.222.100) Could not read server header (192.168.77.77/mail.pulse.com.au:80) what's wrong ?

Author:	hege [ 10 Dec 2008 11:22 ]
Post subject:	Re: Could not send header to browser
Read FAQ. viewtopic.php?f=2&t=4 Reduce LOGLEVEL.

Author:	badm4n [ 10 Dec 2008 11:30 ]
Post subject:	Re: Could not send header to browser
yes i know i use false 1 i set full log because that website already whitelisted ( because same reason ) but still can accessed "parentproxy" down but when i bypass ( direct / disable havp only ) to my proxy it's have zero problem

Author:	badm4n [ 17 Dec 2008 07:13 ]
Post subject:	Re: Could not send header to browser
any solution ? http://my.blog.or.id/v2/10122008/1-serv ... -squid-27/

Author:	badm4n [ 16 Feb 2009 14:28 ]
Post subject:	Re: Could not send header to browser
any answer ? it's look like the whitelist not work

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

[Solved] Could not send header to browser http://havp.hege.li/forum/viewtopic.php?f=3&t=403	Page 1 of 2

Author:	karesmakro [ 18 Feb 2009 11:49 ]
Post subject:	Re: Could not send header to browser
What's your problem? You open more then one thread about one problem, give no response about my suggestions. To this day, i don't know about your squid version. How can anybody help you? What dou you expect? Help was offered to you. See faq's. Still, there is any problem in your squid configuration and no log messages to this day ... Please forgive me, but people spend time to help you, but no cooperation .. Edit found squid version in your blog

Author:	badm4n [ 18 Feb 2009 12:42 ]
Post subject:	Re: Could not send header to browser
karesmakro wrote: What's your problem? You open more then one thread about one problem, give no response about my suggestions. To this day, i don't know about your squid version. How can anybody help you? What dou you expect? Help was offered to you. See faq's. Still, there is any problem in your squid configuration and no log messages to this day ... Please forgive me, but people spend time to help you, but no cooperation .. Edit found squid version in your blog sorry about 2 topic it's actually viewtopic.php?f=3&t=404 i have problem some site i put on whitelist but havp still do scan on the site at viewtopic.php?f=3&t=403 i wrote that is log from error log any solution ?

Author:	karesmakro [ 18 Feb 2009 12:53 ]
Post subject:	Re: Could not send header to browser
As far as i know, whitelisted entries are not scanned but have an entry in messages and should be ignored. If you don't want, that the traffic of your exception site goes through havp, you have to make a proxy exception in squid by direct access. At point 2 of your question: is it possible, that you use only one nic for incoming and outgoing traffic? And which versions of havp and clamav are you actually using? greetings

Author:	karesmakro [ 18 Feb 2009 12:58 ]
Post subject:	Re: Could not send header to browser
I saw your havp configuration a second time and recommend you, to change parent proxy to 127.0.0.1, if squid is on the same machine. I remember of some problems, if you're using nic ip adress ... and why you are using 2 cache peer addresses? Perhaps this solves your problem ... ?

Author:	badm4n [ 18 Feb 2009 13:15 ]
Post subject:	Re: Could not send header to browser
which versions of havp and clamav are you actually using? HAVP Version: 0.89 (squid/2.7.STABLE3) root@castor:/etc/sysconfig/htb# tail -f /var/log/havp/error.log 18/02/2009 17:13:08 === Starting HAVP Version: 0.89 18/02/2009 17:13:08 Running as user: havp, group: havp 18/02/2009 17:13:08 Use parent proxy: 127.0.0.1:2012 18/02/2009 17:13:08 Use transparent proxy mode 18/02/2009 17:13:08 --- Initializing ClamAV Library Scanner 18/02/2009 17:13:08 ClamAV: Using database directory: /usr/local/share/clamav 18/02/2009 17:13:09 ClamAV: Loaded 511059 signatures (engine 0.94.2) 18/02/2009 17:13:09 ClamAV Library Scanner passed EICAR virus test (Eicar-Test-Signature) 18/02/2009 17:13:09 --- All scanners initialized 18/02/2009 17:13:09 Process ID: 31573 Whitelist working Browser (User-Agent) Exposed Headers Values Accept: text/html,application/xhtml+xml,application/xml;q=0.9,/;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Accept-Encoding: gzip,deflate Connection: keep-alive Cache-Control: max-age=0 X-Forwarded-For: 192.168.222.222, 127.0.0.1 Via: 1.0 HAVP, 1.0 castor.gpi-g.com:80 (squid/2.7.STABLE3) the parent proxy changed to 127.0.0.1 and HAVP still running Perhaps this solves your problem ... ? : YES... Thank you verymuch so the point of my problem is comming from parent proxy address ?

Author:	karesmakro [ 18 Feb 2009 13:29 ]
Post subject:	Re: Could not send header to browser
Yes. As i remember, i had the same problem long time ago ... I'm happy, i could help you! Can you please change subject to solved? greetings, Kare

Author:	badm4n [ 19 Feb 2009 09:07 ]
Post subject:	Re: Could not send header to browser
karesmakro wrote: Yes. As i remember, i had the same problem long time ago ... I'm happy, i could help you! Can you please change subject to solved? greetings, Kare yes hmmmm oot : kare : you told me that you has same problem... is you running havp and squid in 1 server too ?

Author:	karesmakro [ 19 Feb 2009 11:08 ]
Post subject:	Re: [Solved] Could not send header to browser
That's right. I've one debian server with squid - havp -clamv and one IPCop in front of my debian server with clamav + havp too. The one on my debian server is for experimental and to prepare configuration for companies. Why this question? greetings, Kare

Author:	badm4n [ 19 Feb 2009 13:25 ]
Post subject:	Re: [Solved] Could not send header to browser
karesmakro wrote: That's right. I've one debian server with squid - havp -clamv and one IPCop in front of my debian server with clamav + havp too. The one on my debian server is for experimental and to prepare configuration for companies. Why this question? greetings, Kare maybe you can share your config squid and havp ? and rc.local maybe ?

Author:	karesmakro [ 19 Feb 2009 14:06 ]
Post subject:	Re: [Solved] Could not send header to browser
Which configuration do you want? I have one with havp and squid configured as a sandwich (which decreases a little bit the performance) and was described in a thread of me where you asked for havp config: http://havp.hege.li/forum/viewtopic.php?f=3&t=399 (next to last thread) or you wanna configuration like havp -> squid, which is simplier to configure. I can't post the whole squid configuration, because there are much of acl's and ncsa authentication. This one is an example, to configure squid -> havp squid.conf Code: acl traffic_all src 0.0.0.0/0.0.0.0 acl Scan_HTTP proto HTTP acl Scan_FTP proto FTP acl NOSCAN dstdomain www.domain_not_to_scan.de always_direct allow NOSCAN cache_peer 127.0.0.1 parent 8080 0 no-query no-digest no-netdb-exchange default cache_peer_access 127.0.0.1 allow traffic_all always_direct allow Scan_FTP never_direct allow Scan_HTTP and in havp.config Code: Port 8080 without any parent proxy entry Hint: do not copy and paste, this is squid configuration from older release! Configuration should be similar, like configuration in the link above. If you decide to want this configuration, let me know and i look at my server to find the correct configuration about squid 2.7!

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