Typing a slash ("/") in the username the login box does not redisplay




Networking: HTTP
7 years ago
a month ago


(Reporter: Volker Berlin, Unassigned)


1.9.2 Branch
Windows Vista

Firefox Tracking Flags

(Not tracked)


(Whiteboard: [necko-would-take])



7 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; de-DE; rv: Gecko/20100722 Firefox/3.6.8 ( .NET CLR 3.5.30729; .NET4.0C)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; de-DE; rv: Gecko/20100722 Firefox/3.6.8 ( .NET CLR 3.5.30729; .NET4.0C)

If the web server use windows authentication then a login box appear by default. If the user type a slash instead a backslash between domain and username then the input is invalid. But the Firefox does not redisplay the login box. You see a 401 error page. Also a reload does not help. You need to close all Firefox windows and restart it. This is different to every other wrong username.

Other browser like Chrome redisplay the login box in this case. The IE8 does not accept a slash because this is ever invalid.

There are 2 possible solutions:
a) Replace a slash ever with a backslash.
b) Redisplay the login box if the 401 error from server come like with every other wrong username.

Reproducible: Always

Steps to Reproduce:
1. Use a web server which request windows authentication
2. Type domaine and user delimited with a slash
Actual Results:  
The login box is hide and show never again.

Expected Results:  
The login box should show again.
Do you either tried shift+reload or ctrl+shift+del->details->only active logins checked ?
Component: General → Networking: HTTP
Product: Firefox → Core
QA Contact: general → networking.http
Version: unspecified → 1.9.2 Branch

Comment 2

7 years ago
This also not help. The only that help is a completely restart of the Firefox or in the web-developer toolbar the menu item "Delete private data | HTTP-Authentication".
Whiteboard: [necko-would-take]
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.