Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Przeszukaj pomoc

Unikaj oszustw związanych z pomocą.Nigdy nie będziemy prosić Cię o dzwonienie na numer telefonu, wysyłanie SMS-ów ani o udostępnianie danych osobowych. Zgłoś podejrzaną aktywność, korzystając z opcji „Zgłoś nadużycie”.

Learn More

Is there an issue with the latest version of FF with HTTPS requests and Proxy authentication?

  • 1 odpowiedź
  • 15 osób ma ten problem
  • 1 wyświetlenie
  • Ostatnia odpowiedź od NoahSUMO

more options

I'm currently working inside a cope network behind a proxy, which requires authentication.

When browsing to websites externally to our network I would usually only be promoted once for authentication details; after that I would never see the prompt again until after restating the browser.

However after the latest update I've found that when visiting HTTPS sites I'm promoted for my login details. But even though I enter the correct information the prompt does not take the details and continually asks until eventually our proxy closes the connection (usually with my account now being locked).

My other browsers (IE, GC) work fine without problems.

Any ideas?

I'm currently working inside a cope network behind a proxy, which requires authentication. When browsing to websites externally to our network I would usually only be promoted once for authentication details; after that I would never see the prompt again until after restating the browser. However after the latest update I've found that when visiting HTTPS sites I'm promoted for my login details. But even though I enter the correct information the prompt does not take the details and continually asks until eventually our proxy closes the connection (usually with my account now being locked). My other browsers (IE, GC) work fine without problems. Any ideas?

Wszystkie odpowiedzi (1)

more options

It could be a regression in Firefox 18 that wasn't present in Firefox 17. The developers are known nowadays for including too many experimental changes and my bet is one of them is causing this.

But to confirm, could you downgrade back to Firefox 17 and still see if it works well with proxy authentication?

Download link:
www.mozilla.org/en-US/products/download.html?product=firefox-17.0.1&os=win&lang=en-US