Closed
Bug 35581
Opened 25 years ago
Closed 25 years ago
Can't login to Yahoo
Categories
(Core :: Networking: Cookies, defect, P3)
Tracking
()
People
(Reporter: ken.horn, Assigned: morse)
References
()
Details
Trying to log in to my mail account - fails - I always get the login screen again.
Not sure of the reason for failure, but looking at the message (POST) sent, i
noticed the cookie http header sent as- cookie: not Cookie: , ie lower case.
Netscape 4.7 uses Cookie:
This may need to be referred to the site, in order to determine the reason for
failure..
Comment 1•25 years ago
|
||
This seems to be a dup of bug 27687.
Just some text copied from 33431:
Reporter, please try the following corrective action to verify that this is
indeed a duplicate: 1) Start up seamonkey 2) Go to the Edit menu and select
Preferences... 3) Click on Advanced->Cookies and Images under the Category menu.
4) In the cookies pane, verify if "Accept cookies that get sent back to the
originating server only" or "Reject all cookeis" are selected. 5) Select "Accept
all cookies". 6) Click OK. 7) Try to log in to yahoo mail. If you are now able
to log in, please mark this bug as Verified. Thanks! (I just tested this now and
was able to log in with no problems)
Assignee | ||
Comment 2•25 years ago
|
||
Turns out that the Cookie: vs cookie: bug had been reported in a separate report
(bug 34952) and the fix checked into the tree last night (before this current
report was filed). But I'm pretty sure that is not the problem here.
I keep seeing this report many times (bug 26787 and all its dups). And each
time the problem has been that the reporter had his pref set to reject foreign
cookies. Yahoo does not let you log in if that pref is set. I'm willing to bet
that's your problem here as well.
It's unfortunate that yahoo does not put up a message telling the user to change
that pref. They are certainly aware of why they refused the login.
*** This bug has been marked as a duplicate of 26787 ***
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Comment 3•25 years ago
|
||
Oops, marked as dup of wrong bug. Reopening.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
Assignee | ||
Comment 4•25 years ago
|
||
And now marking dup correctly. It should be bug 27687.
*** This bug has been marked as a duplicate of 27687 ***
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Comment 5•25 years ago
|
||
Oops again. I didn't see mielke's comment when I added mine (we made them at
about the same time independently). He's saying the same thing that I said.
Not sure if my email got through..
I checked the cookie setting - accept all cookies was the setting. Still
have the problem. I'll try and narrow down the conditions tomorrow if I can.
Thanks for the prompt response. (Anyone would think you were trying to get a
product out or something.. !)
I'm running the Nightly from night of 04/11.
Not sure if this is still dup. I've just read the dup bug report - looks pretty
similar. Will try a fresh profile tomorrow.
Ken
You need to log in
before you can comment on or make changes to this bug.
Description
•