Closed
Bug 44865
Opened 25 years ago
Closed 25 years ago
Yahoo mail only works if cookies are set permissively
Categories
(Core :: Networking: Cookies, defect, P3)
Tracking
()
People
(Reporter: jimsantelmo, Assigned: morse)
References
()
Details
Yahoo Mail had never worked for me, and Mozilla is in good enough shape
otherwise so I decided to submit a bug on it. The problem is that if cookie
control is set to anything other than 'Accept All Cookies' in the
preferences/Cookies and Images dialog, apparently mozilla is quite literal
about the server, differentiating between mail.yahoo.com and yahoo.com. This
is a variation from the Netscape behavior which breaks Yahoo mail.
I did a bugzilla search on cookie and one on yahoo, and didn't find anything
that seemed like a clear match to this. If this is known, please delete this
bug and send me the # of the original one so I can add to the cc list.
Using a browser that accepts all cookies is not an acceptable option for me.
My build is from CVS, made within the last few days.
Sounds a lot like bug 8743, marked fixed around a year ago.
Summary: Yahoo mail only works if cookies are set permissively → Yahoo mail only works if cookies are set permissively
Assignee | ||
Comment 2•25 years ago
|
||
Can you read your yahoo mail with 4.x when you have the pref set to reject
foriegn cookies?
If no, then there is no bug. This is the intended behavior. Problem is with
the site, not with the pref setting.
If yes, then I have an explaination. There was a minor change in semantics for
this pref between 4.x and seamonkey. In 4.x, the pref affected the ability of a
foreign site to set a cookie. But foreign sites would still be sent any of
their own cookies that they had previously set. In seamonkey that loophole was
closed and the pref affects both setting and receiving of cookies. So if it is
working for you in 4.x, that means that the cookie probably got set on you
long before you set the pref, and now is being dutifully sent back. So remove
the cookie (by editing the cookies.js file with the browser closed), set the
pref to reject-foreign, and try again. I'm willing to bet that your behavior
will now be identical to what you are seeing in seamonkey.
BTW, although there is some similarity, I don't believe this has anything to do
with bug 8743. Like you said, that bug was fixed over a year ago. But it is a
dup of the following bugs: 28795, 27687, 28545
*** This bug has been marked as a duplicate of 27687 ***
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
> ------- Additional Comments From dark@c2i.net 2000-07-08 09:31 -------
> Sounds a lot like bug 8743, marked fixed around a year ago.
I don't think this is a dup of that, which appears to occur when
'accept all cookies' is set:
qq[
Site visited : http://mail.yahoo.com
M7 Preference set : enable Java, enable JavaScript, accept all cookies
error from site : An Error Occurred Setting Your User Cookie
];
The bug I'm reporting goes away when cookies goes from
'originating server only' to 'all'. If you look at the cookie-viewer
while dealing with mail.yahoo.com, you see cookies set by both yahoo.com
and mail.yahoo.com. It appears that netscape-4 is treating these both as a
single server for the purposes of cookies, and mozilla isn't. Mozilla is
probably correctly implementing the described behavior, so perhaps the
description and behavior should be changed to 'originating domain only'.
Guess that would have to be based on dns-parsing, as the ip address won't
do it:
yahoo.com: 204.71.200.243
mail.yahoo.com:216.115.105.216
I don't know if yahoo.com needs the mail.yahoo.com cookies. Maybe
sending yahoo.com cookies to *.yahoo.com would be adequate.
..some experimenting:
a cookies from mail.yahoo.com is essential. That can't be set without
permissive cookies.
If one removes the cookies from yahoo.com, the session expires, so they
are essential also. So for mail.yahoo.com to work, it looks like
cookie-permissiveness within *.yahoo.com is required.
BTW, I notice the one this is marked as a dupe of. I don't know why searches
on 'cookie' and 'yahoo' didn't get me to them. If you merge them, please keep me
on a cc: list so I can track. I added myself to the one you marked this as a
dupe of.
You need to log in
before you can comment on or make changes to this bug.
Description
•