Astaro User Bulletin Board
Go Back   Astaro User Bulletin Board > Astaro Gateway Products > Web Security: HTTP/HTTPS/FTP, IM/P2P, Web Filtering and Antivirus

Welcome to the Astaro User Bulletin Board.
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 06-24-2009, 11:07 AM
Member
 
Join Date: Sep 2008
Posts: 63
Default Program Update Failing

Hi,

Trying to get ZoneAlarm update for my PC firewall but it keeps failing. When I check HTTP filter logs, I see the following:

2009:06:24-06:03:03 Astaro httpproxy[3926]: id="0064" severity="info" sys="SecureWeb" sub="http" name="web request blocked, forbidden file extension detected" action="block" method="GET" srcip="192.168.10.2" user="" statuscode="403" cached="0" profile="REF_DefaultHTTPProfile (Default Proxy)" filteraction="REF_DefaultHTTPCFFAction (Default content filter action)" size="2394" time="68 ms" request="0xb2937a58" url="http://dl4.zonealarm.com/u/dlr/bin/free/1025_en/zaSetup_80_298_000_en.exe?app=inclient&date=1" exceptions="" error="" category="175" categoryname="Software/Hardware" extension="exe" filename="zaSetup_80_298_000_en.exe" reason="extension"

I've added exceptions for the hostname for extension blocking but it still gives the same error when I attempt to run the update .exe from my desktop. Huh?
Reply With Quote
  #2 (permalink)  
Old 06-24-2009, 12:46 PM
svens's Avatar
Senior Member
 
Join Date: Nov 2005
Posts: 260
Default

Quote:
Originally Posted by atarso View Post
Hi,

Trying to get ZoneAlarm update for my PC firewall but it keeps failing. When I check HTTP filter logs, I see the following:

2009:06:24-06:03:03 Astaro httpproxy[3926]: id="0064" severity="info" sys="SecureWeb" sub="http" name="web request blocked, forbidden file extension detected" action="block" method="GET" srcip="192.168.10.2" user="" statuscode="403" cached="0" profile="REF_DefaultHTTPProfile (Default Proxy)" filteraction="REF_DefaultHTTPCFFAction (Default content filter action)" size="2394" time="68 ms" request="0xb2937a58" url="http://dl4.zonealarm.com/u/dlr/bin/free/1025_en/zaSetup_80_298_000_en.exe?app=inclient&date=1" exceptions="" error="" category="175" categoryname="Software/Hardware" extension="exe" filename="zaSetup_80_298_000_en.exe" reason="extension"

I've added exceptions for the hostname for extension blocking but it still gives the same error when I attempt to run the update .exe from my desktop. Huh?
At least at that time the proxy didn't know anything about that exception - otherwise the exception field in the logline above would show that. Does it work if you switch the off and on again? Can you show us your exception?

Regards,

Sven.
__________________
Sven Schnelle
Software Architect
Astaro AG
Reply With Quote
  #3 (permalink)  
Old 06-26-2009, 02:00 AM
Member
 
Join Date: Sep 2008
Posts: 63
Red face

It dawned on my the instant I submitted the post!

Hopefully it helps someone else in the future at least )

I was specifying:

http://dl4.zonealarm.com/u/dlr/bin/f...nclient&date=1

as the URL for the exception, but really it should be:

http://dl4.zonealarm.com/u/dlr/bin/free/1025_en/

I also specified a file extension exception for the *.exe extension (not sure if that was needed though since I exempted the URL?)
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT. The time now is 12:21 AM.

 

Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2010, Jelsoft Enterprises Ltd.


These pages are specifically maintained for the discussion of firewall issues within the Open Source community, and might already reflect new alpha/beta releases under development. Please refer to our product specifications for the functionality of the actual release. Discussions of new/enhanced functionality does not constitute a commitment of Astaro, to integrate this functionality into future releases. issues within the Open Source community, and might already reflect new alpha/beta releases under development. Please refer to our product specifications for the functionality of the actual release. Discussions of new/enhanced functionality does not constitute a commitment of Astaro, to integrate this functionality into future releases.