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.

Avatar for Username

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.

Why doesn't FF doesn't present user/password dialog in response to 401?

  • 2 antwoorde
  • 1 het hierdie probleem
  • 2 views
  • Laaste antwoord deur pcm42

pcm42
pcm42
more options

We have an embedded web server which requires authentication for some pages (eg; firmware upload). We can't afford the footprint of SSL. We have been using Digest Authentication. This works for Opera and Chrome.

Wireshark capture available upon request

We have an embedded web server which requires authentication for some pages (eg; firmware upload). We can't afford the footprint of SSL. We have been using Digest Authentication. This works for Opera and Chrome. Wireshark capture available upon request

Gekose oplossing

Issue resolved.

After a server sends a 401 response, it closes the socket. The browser should prompt for the user/password, open a new socket, reissues the request with the new Authorization gathered from the prompt added to the header.

When my server was closing the socket (following the 401), I was using RST (no socket timeouts). Works fine for IE11, Safari, Chrome, Opera 57. Just failed for FF.

I modified my server to use a normal socket close. The user/password dialog now works as expected, and FF reissues the request as expected.

Thanks!

Lees dié antwoord in konteks 👍 0

All Replies (2)

hellosct1
hellosct1
more options

Hi,

there is a bugzilla that has been reopened and a solution that is brought


https://bugzilla.mozilla.org/show_bug.cgi?id=472823

I share the number for you to watch

pcm42
pcm42 Vraag-eienaar
more options

Gekose oplossing

Issue resolved.

After a server sends a 401 response, it closes the socket. The browser should prompt for the user/password, open a new socket, reissues the request with the new Authorization gathered from the prompt added to the header.

When my server was closing the socket (following the 401), I was using RST (no socket timeouts). Works fine for IE11, Safari, Chrome, Opera 57. Just failed for FF.

I modified my server to use a normal socket close. The user/password dialog now works as expected, and FF reissues the request as expected.

Thanks!