This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Proxy authorization prompt only for certain URLs when using Firefox

Hello,

ASG220 v8.202
Transparent mode w/AD 2003 SSO
Firefox 10.0, Internet Explorer 8, Google Chrome 16.0

We are experiencing a very strange issue.  Certain URLs when accessed under Firefox cause a prompt for Proxy authentication.  We enter valid credentials but it rejects them and after a number of retries, locks out the AD account.

An example is - Flying Clusters: A Glance at Real-Time Replication From MySQL To Oracle

Here are the corresponding block lines from the Web Filtering log:

2012:02:03-11:30:42 asg httpproxy[6718]: id="0002" severity="info" sys="SecureWeb" sub="http" name="web request blocked" action="block" method="GET" srcip="" dstip="" user="" statuscode="407" cached="0" profile="REF_gAYWStHmik (Main)" filteraction=" ()" size="5529" request="0xc6dd2d08" url="r1rk9np7bpcsfoeekl0khkd2juj27q3o-a-fc-opensocial.googleusercontent.com/.../ifr


2012:02:03-11:30:42 asg httpproxy[6718]: id="0002" severity="info" sys="SecureWeb" sub="http" name="web request blocked" action="block" method="GET" srcip="" dstip="" user="" statuscode="407" cached="0" profile="REF_gAYWStHmik (Main)" filteraction=" ()" size="5529" request="0xc6dd2d08" url="r1rk9np7bpcsfoeekl0khkd2juj27q3o-a-fc-opensocial.googleusercontent.com/.../ifr


Note: I've manually removed the "srcip" and "user" data

Accessing the same URL under Internet Explorer or Chrome works fine.

Firefox is set to pull proxy settings from the system proxy settings.

I'm not sure what's causing the issue, but we seem to be spending more and more time unlocking peoples AD accounts as seeminlgy random pages are blocked.

Has anyone seen this behaviour before or know what the cause may be?

Many Thanks,

Paul


This thread was automatically locked due to age.
Parents
  • I don't know if Paul's problem is the same.  In a case I just handled, the user's 'LAN Settings' had an FQDN that wasn't resolvable to the IP of "Internal (Address)" - correcting that got rid of the "407" problem.

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Reply
  • I don't know if Paul's problem is the same.  In a case I just handled, the user's 'LAN Settings' had an FQDN that wasn't resolvable to the IP of "Internal (Address)" - correcting that got rid of the "407" problem.

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Children
No Data