Closed Bug 276276 Opened 20 years ago Closed 20 years ago

Clicking a URL in a mail message launches the URL but does not send cookies to site

Categories

(SeaMonkey :: MailNews: Message Display, defect)

1.7 Branch
x86
Windows 2000
defect
Not set
major

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 267378

People

(Reporter: dan, Assigned: sspitzer)

Details

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

After upgrading from 1.7.3 to 1.7.5 if I am sent a URL in an e-mail and I click
on the URL to launch it the page is opened in Mozilla browser as normal. 
However if the URL being opened is a site that uses cookies and a cookie has
already been set (such as forums that you have already logged onto) it seems
that the cookie is not sent back to the site when opening the URL from the mail
client and you invariably get a "you are not logged in" message!

Reproducible: Always




This is stopping me from using Mozilla v1.7.5 as I use a lot of forums which
e-mail you when topics have been updated, normally you would then click on the
URL in the e-mail and reply back but this is not possible due to this bug.
Strangely, right clicking on the URL and selecting "Open Link In A New Window"
or "Open Link In A New Tab" works as it should but left clicking on the URL is
broken as per the bug.
Version: unspecified → 1.7 Branch
There are several known issues around clicks from the mail program.  At least 
one of these issues was addressed by the fix for bug 267378; it's quite possible 
that has fixed this problem as well.

Try the latest 1.7 build:
  http://ftp.mozilla.org/pub/mozilla.org/mozilla/nightly/latest-1.7/

If this problem is solved, please mark this bug as dupe of 267378.
Bug was fixed when Bug 267378 was fixed

*** This bug has been marked as a duplicate of 267378 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.