Avatar for Username

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

Ce sujet de discussion a été archivé. Veuillez poser une nouvelle question si vous avez besoin d’aide.

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

  • 1 réponse
  • 15 ont ce problème
  • 1 vue
  • Dernière réponse par NoahSUMO

CastorUK
CastorUK
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?

Toutes les réponses (1)

NoahSUMO
NoahSUMO
  • Top 25 Contributor
  • Moderator
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