Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Avatar for Username

Шукати в статтях підтримки

Остерігайтеся нападів зловмисників. Mozilla ніколи не просить вас зателефонувати, надіслати номер телефону у повідомленні або поділитися з кимось особистими даними. Будь ласка, повідомте про підозрілі дії за допомогою меню “Повідомити про зловживання”

Докладніше

Ця тема перенесена в архів. Якщо вам потрібна допомога, запитайте.

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

  • 2 відповіді
  • 1 має цю проблему
  • 34 перегляди
  • Остання відповідь від 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

Обране рішення

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!

Читати цю відповідь у контексті 👍 0

Усі відповіді (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 Власник питання
more options

Вибране рішення

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!