Astaro User Bulletin Board
Go Back   Astaro User Bulletin Board > Closed Forums (read only) > ASG V7.500 BETA (closed)

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.

 
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 06-25-2009, 05:38 AM
javelin's Avatar
Senior Member
 
Join Date: Nov 2002
Location: Gateway to the West
Posts: 172
Red face HTTP acces to some sites fail

Hello all.

I'm not sure if this is a bug or not but since I've upgraded into 7.460, HTTP access to some sites fails.

For example, if I go to yahoo.com, scottrade.com, charles-schwab.com, or bankofamerica.com, the status bar on the browser just stays on "Waiting for blah.com" and it just goes on forever and never times out. If I go to ebay.com, newegg.com or some other sites, there's no problem.

Now that I've restored back to 7.450, access to the aforementioned sites works just fine and response time in split-seconds.

I saved a copy of the HTTP content log on 7.460 and compared with 7.450 accessing yahoo.com and there's no difference.

See the following entries.

7.460:
2009:06:24-22:06:24 sidewall httpproxy[3925]: id="0001" severity="info" sys="SecureWeb" sub="http" name="http access" action="pass" method="GET" srcip="192.168.1.30" user="" statuscode="302" cached="0" profile="REF_DefaultHTTPProfile (Default Proxy)" filteraction="REF_DefaultHTTPCFFAction (Default content filter action)" size="83" time="162 ms" request="0xb186cfd8" url="http://mail.yahoo.com/" exceptions="auth,content,url,mime" error=""

7:450:
2009:06:24-23:16:03 sidewall httpproxy[3889]: id="0001" severity="info" sys="SecureWeb" sub="http" name="http access" action="pass" method="GET" srcip="192.168.1.30" user="" statuscode="301" cached="0" profile="REF_DefaultHTTPProfile (Default Proxy)" filteraction="REF_DefaultHTTPCFFAction (Default content filter action)" size="79" time="190 ms" request="0xa8c028e8" url="http://www.mail.yahoo.com/" exceptions="auth,content,url,mime" error=""

My first thought was the HTTP content. Given that there are no errors and the exceptions objects are identical, I'm thinking it could be something else. Any ideas?

Thanks,
jav
  #2 (permalink)  
Old 06-25-2009, 06:45 AM
 
Join Date: Jun 2009
Posts: 0
Default

Code:
Astaro Beta Report
--------------------------------
Version: 7.460
Type: BUG
State: NOTABUG
Reporter: javelin
Contributor: 
MantisID: 
--------------------------------

Last edited by andyk007; 10-09-2009 at 02:08 PM.
  #3 (permalink)  
Old 07-02-2009, 02:22 PM
Wizard
 
Join Date: Dec 2006
Posts: 653
Default

Hi,

there is a different. In 7.460 you get a status code 302 and in 7.450 you get a status code 301.

302 means action move. In most cases for example if you get forwarded from mail.yahoo.com to another url.

301 means that forwarding to another url is permanent

wou will find a good explanation on Status codes in HTTP

But both error codes are normal and should not drop any traffic. If I try to browse your url through the proxy with 7.460 it works without problems. Could you maybe send us some screenshots of your settings?

greetings
Andreas
 

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:57 PM.

 

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.