From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.6+) Gecko/20011126 BuildID: 2001112603 When I try to sign in to yahoo(http://mail.yahoo.com) by supplying my Yahoo! Id and Password and click the Sign In button I get an alert box saying 'login.yahoo.com could not be found. Please check the name and try again.' So effectively I can't login. Reproducible: Always Steps to Reproduce: 1. go to http://mail.yahoo.com (you need to have a valid Yahoo! account) 2. fill up the Yahoo! Id and Password 3. click the Sign In button Actual Results: An alert box pops up saying 'login.yahoo.com could not be found. Please check the name and try again.' Expected Results: I should have login and directed to my mailbox. This works ok on IE 6.0

odd...alas, i don't think XP Apps is the right component for this issue. asa, d'you know where this ought to live?

Reporter: 1: Have you enabled all cookies? 2: Did you install PSM? 3: Are you using a proxy?

Reply to comment #1 How about changing the component to Form Submission. Reply to comment #2 - Yes I have enabled all cookies - I use a nightly 11/26 and I think that PSM comes with it already. I don't use installer builds, I like the unzip and run method better. - Yes I use a proxy and it is properly configured, so far that is the only site I'm having the problem with. As I said in the bug report this works properly in IE 6.0 and it used to work properly in Mozilla, so there must have been some regression. This is also a problem in the 11/28 build.

When you say the proxy is properly configured, you're aware of bug 38488 of course?

The proxy I am connecting to is squid, I don't use junkbuster, and as I said before this used to work in the previous builds. Just a note on the status bar it says 'Resolving host login.yahoo.com', so I assume that it is indeed attempting to resolve login.yahoo.com but is unable to for some reason.

if disabling squid makes the page load OK: perhaps related to bug 92742

->networking

I found the solution to the problem, I was not able to set the SSL proxy. Once I set that it worked flawlessly. Thanks for your help. I think you can safely change the state of this bug to RESOLVED INVALID.

Proxy used but SSL proxy setup missing in users installation: Resolving as invalid per reporters comment. Roderick: Just in case.. If there is some issue with filling in SSL proxy field in prefs, please file as a separate bug.

I don't think there is any issue with filling in SSL proxy field in prefs. But I believe that 'if' ever the networking code 'is able' to detect an error in connecting due to SSL then it would be better if the the alert message would say something about SSL so that the user can narrow down the possible wrong configuration. Just a thought =)

v

really caused by bug 56629.