290507 - Cookies not set or sent when clicking an external link in an e-mail.

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Berk Akinci]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041217
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041217

When clicking a link in Mozilla Mail, cookies are not set or sent to the HTTP
server.  Cookies are not allowed for mail messages, but clicking a link opens
them in Navigator.  In Navigator, cookies should be allowed (per my preferences).

Reproducible: Always

Steps to Reproduce:
1) Send yourself e-mail with a link to a web page that sets/requires cookies. 
Eg: http://www.netflix.com
2) Click on the link in the e-mail


Actual Results:  
Page loads in Navigator window, but doesn't allow set or send cookies.  It
appears to follow the behavior defined by
network.cookie.disableCookieForMailNews.  In the www.netflix.com example, you
are forwarded to the page "http://www.netflix.com/entryTrap.html" with
instructions to enable cookies.  Ethereal trace shows that the cookies were not
sent.  Clearing the cookies shows that the cookies sent by netflix are not set
either.


Expected Results:  
Should load in a Navigator window, honoring cookie preferences for Navigator.


Preference network.cookie.disableCookieForMailNews is set to "true" by default
(I found no UI for this pref).  Setting to "false" makes the above test work
successfully.

Right-clicking the link and selecting "Open Link in New Window" makes the test work.

Comment 1

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 2

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.