This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

Proxy Authorization Required. Firefox does not ask for a proxy username and password.

  • 4 antwoorde
  • 24 hierdie probleem
  • 1 view
  • Laaste antwoord deur bruce.hodge

more options

I am using firefox on mac with manual proxies and have provided the proxy address and port. I have set the proxy in Firefox->Preferences->Advanced->Network. This proxy requires authentication But firefox does not prompt me for credentials of this proxy. It just throws a page that says "Proxy Authorization Required" and "Description: Authorization is required for access to this proxy"

I have tried the following to no effect. 1) Clearing all the profiles in ~/Library/Profiles folders 2) Clearing profiles.ini file. 3) Setting the proxy along with username and password in System preferences and make firefox use system proxies instead of manual proxies.

Right now I am downloading firefox 13 beta to see if this solves the problem. Any workaround available for FF12.0?


Any help is greatly appreciated.

Thanks.


EDIT:: Tried with FF 13 beta. Same problem

I am using firefox on mac with manual proxies and have provided the proxy address and port. I have set the proxy in Firefox->Preferences->Advanced->Network. This proxy requires authentication But firefox does not prompt me for credentials of this proxy. It just throws a page that says "Proxy Authorization Required" and "Description: Authorization is required for access to this proxy" I have tried the following to no effect. 1) Clearing all the profiles in ~/Library/Profiles folders 2) Clearing profiles.ini file. 3) Setting the proxy along with username and password in System preferences and make firefox use system proxies instead of manual proxies. Right now I am downloading firefox 13 beta to see if this solves the problem. Any workaround available for FF12.0? Any help is greatly appreciated. Thanks. EDIT:: Tried with FF 13 beta. Same problem

Gewysig op deur Sanjay

Gekose oplossing

I managed to solve this one. Just set the following values to false in about:config.

  1. network.automatic-ntlm-auth.allow-proxies
  2. network.negotiate-auth.allow-proxies

Hope this helps someone out there :).

Lees dié antwoord in konteks 👍 14

All Replies (4)

more options

Gekose oplossing

I managed to solve this one. Just set the following values to false in about:config.

  1. network.automatic-ntlm-auth.allow-proxies
  2. network.negotiate-auth.allow-proxies

Hope this helps someone out there :).

Gewysig op deur Sanjay

more options

The problem still exists in FF15 on the MAC. The ntml fix works, but it would be nice if it worked out of the box. Is there a way to make the change and package FF up for redistribution with network.automatic-ntlm-auth.allow-proxies = False ?

more options

Use a mozilla.cfg file in the Firefox program folder to lock prefs or specify new (default) values.

Place a file local-settings.js in the defaults/pref folder where you also find the file channel-prefs.js to specify using mozilla.cfg.

pref("general.config.filename", "mozilla.cfg");
pref("general.config.obscure_value", 0); // use this to disable the byte-shift

See:

You can use these functions in mozilla.cfg:

defaultPref();  // set new default value
pref();         // set pref, but allow changes in current session
lockPref();     // lock pref, disallow changes
more options

Thanks Cor-el, A little more info if anyone is trying to fix the original bug. If the Blue coat proxy is set to authenticate via LDAP it works no problem. If the blue coat is set to IWA and use AD it doesn't work. The browser is either having issues with the hand over from one auth method to the other or it doesn't like the AD method????