after logging into Yahoo mail... error recieved. 'Can't Set Cookie' have check that Mozilla M5 have cookie allowed.

Looks like somebody set up the preference pane incorrectly so that "accept all cookies" was given the enumeration type of "disable cookies". To really get the behavior of accepting cookies, you would have had to check off "accept only cookies ... " because that was given the enumeration type of "accept all cookies." Fix is to change the enumeration types in xpfe/AppCores/xul/pref-advanced.html. I have the fix and will check it in as soon as the tree opens. Marking bug as fixed.

verified cookies working fine win/linux - prefs are correct

try out M6 and have the following reponds. login to mail.yahoo.com they have a framed page. left frame goes in successfully but right frame experienced some cookies problem.

I get the two frames successfully with no cookie problems. I did get asked twice if I wanted to allow cookies to be set so I know that the site did indeed set two cookies and they got set successfully. Check to make sure that you didn't have cookies disabled. Also check to make sure that you don't have the yahoo site on the list of sites from which you do not accept cookies (look in the cookperm.txt file). I should mention that I did have a problem getting to the yahoo mail page but that had nothing to do with cookies. When I clicked on yahoo mail from the main yahoo page, nothing happened. So I had to look in the page source to see where they wanted to go (http://www.yahoo.com/homet/?http://mail.yahoo.com) and manually type that into the location field. But this is a totally different problem than the one reported by slok00. This smells like a netlib problem and netlib is being completely rewritten anyway so I won't file a bug report on this. If anyone else experiences this problem, and wants to file a bug report agains netlib on it, go ahead and do so.

I think this was probably a dup that got fixed, but marking verified anyways.

Yes, now that I am more familiar with the cause of bug 8743, I realize that this is a dup of that bug. So, in fact, I'm going to reopen this and then mark it resolved as a duplicate.

*** This bug has been marked as a duplicate of 8743 ***

alrighty, verified as a dup then

Verified Dup