Closed Bug 260476 Opened 20 years ago Closed 20 years ago

Livemark failure with Proxies with authentication

Categories

(Firefox :: Bookmarks & History, defect)

x86
Windows 2000
defect
Not set
major

Tracking

()

VERIFIED DUPLICATE of bug 266348

People

(Reporter: praveen.bugzilla, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20040913 Firefox/0.10 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20040913 Firefox/0.10 I am using Firefox 1.0PR. Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20040913 Firefox/0.10 Failure of the Livemark loading with proxies that require NTLM authentication. My basic deduction is that Livemark doesnt ask for proxy authentication if it hasnt been done even once and just fails to load. This is can be frustrating as user doesnt get any feedback and misleads from the actual problem Reproducible: Always Steps to Reproduce: 1. Set proxy to a server that requires authentication 2. Now close FF and launch with home page that doesnt access the net 3. Once, FF is launched as first action try opening a livemark. Actual Results: Livemark shows up as Livemark loading failed. But, if any website is opened and proxy authenticated for the first time. Then, if Livemarks are opened then load without any problem. Expected Results: FF should throw up the authentication dialog so, user can enter username and password. Then, FF should proceed to load the Livemark.
Assignee: vladimir → vladimir+bm
Confirmed using Gecko/20041107 Firefox/1.0
Status: UNCONFIRMED → NEW
Ever confirmed: true
Version: unspecified → Trunk
*** This bug has been marked as a duplicate of 266348 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
Assignee: vladimir+bm → nobody
sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs, filter on "beltznerLovesGoats" to get rid of this mass change
QA Contact: mconnor → bookmarks
You need to log in before you can comment on or make changes to this bug.