Closed Bug 157771 Opened 22 years ago Closed 19 years ago

clicking on link in message window hits the server twice

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: deneen, Unassigned)

References

Details

Clicking on a link in the message window hits the server twice.  

This is problematic for sites which email a link to verify an account, as some
of them check to see if an account has already been verified.  This would
confuse a lot of people.
right clicking on a link and selecting "Open in New Window", it does not double tap.

I re-checked this in 2002071608 trunk, and it still happens there as well.
Looks like good ol' cache problem. 
Please look at bug 121084 and check if your bug is sensitive to cache settings
in the same manner. If yes, then it's most likely a dupe.
My cache setting is set to "When the page is out of date"

People mentioned that they had the image loading problem with multiple cache
settings.

I don't understand why right clicking and choosing "Open in new window" would
change anything in the way the cache works.
*** Bug 185173 has been marked as a duplicate of this bug. ***
Can you provide a specific site with a specific with email link?
I believe this might be either fixed by bug 121084 or will be
fixed with bug 89419, but would like to check.
(seth sorry to poke my nose in this)
I don't have a specific site on hand, but try sending yourself an email with a
url in it, pointing to a server where you can tail the logs.

Here is what my logs look like:

209.236.166.168 - - [03/Apr/2003:14:56:05 -0500] "GET /fsdfsd HTTP/1.1" 404 96
"-" "Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4a) Gecko/20030403"
209.236.166.168 - - [03/Apr/2003:14:56:06 -0500] "GET /fsdfsd HTTP/1.1" 404 96
"-" "Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4a) Gecko/20030403"
209.236.166.168 - - [03/Apr/2003:14:56:06 -0500] "GET / HTTP/1.1" 200 335 "-"
"Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4a) Gecko/20030403"
209.236.166.168 - - [03/Apr/2003:14:56:06 -0500] "GET /images/splash.gif
HTTP/1.1" 200 143362 "http://www.snuggleexpress.com/" "Mozilla/5.0 (Windows; U;
Windows NT 5.0; en-US; rv:1.4a) Gecko/20030403"


I only clicked once.  I have the server set up with a custom 404 redirect.  The
logs show only one redirect happening... 
just an additional note..

I don't know if this makes a difference.. I did not read the maybe-related bugs
very thoroughly, but this one does not deal with any images.  Obviously the
cache is involved in both cases.. but this is a fresh made-up link.  It
shouldn't ever be in the cache when you click on it.

Product: Browser → Seamonkey
Assignee: sspitzer → mail
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/
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.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.