158783 - [RFE] Option to have bookmark update check use MD5 hash sum

Status: RESOLVED EXPIRED

(SeaMonkey :: Bookmarks & History, enhancement)

Description

[Anthony DeRobertis]

I'm running 2002052918 and have a bookmark sheduled to tell me when its been
updated. The content comes from PHP which unfortunately sets the Last-Modified:
header to the current date/time. While strictly speaking a server bug, it is
fairly common with generated pages.

This makes Mozilla think that the page has always changed. If mozilla could keep
around and compare the MD5 (or SHA1, or whatever) of the page then it would not
be fooled by PHP.

This could either be an option ("quick check" or "thorough check") or automatic
when there is a Pragma: no-cache, Cache-Control: against caching, Expires:
header that makes the page non-cachable, or Last-Modified: date of approximately
now (maybe within 10min to catch misset clocks).

Comment 1

[Jo Hermans]

Aren't we using the 'ETag' from HTTP/1.1 ?

Comment 2

[Wesha]

I think it would make sense to use bug 23212 for these suggestions, and not a
separate one, so the developers don't have to shuffle through the database...

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

Comment 3

[Anthony DeRobertis]

Wesha: It'd probably be easier to use bug 23212 as a tracking bug. There is no
easy way to go through all the duplicates of a bug, nor should there be.
Duplicates shouldn't be about different issues, after all. I have re-opened and
marked a blocker of bug 23212.

Jo Hermans: This server doesn't send an ETag, so probably not. For your
reference, here are the headers:
  lynx -head -dump http://www.animemusicvideos.org/legacy/video.php?v=9080
  HTTP/1.1 200 OK
  Date: Tue, 23 Jul 2002 19:11:30 GMT
  Server: Apache/1.3.19 (Unix)  (Red-Hat/Linux) mod_fastcgi/2.2.10 mod_gzip/1.3.1
  9.1a mod_ssl/2.8.1 OpenSSL/0.9.6 PHP/4.0.6 mod_perl/1.24_01 FrontPage/5.0.2
  X-Powered-By: PHP/4.0.6
  Expires: Mon, 26 Jul 1997 05:00:00 GMT
  Last-Modified: Tue, 23 Jul 2002 19:11:30 GMT
  Cache-Control: post-check=0, pre-check=0
  Pragma: no-cache
  Content-Encoding: gzip
  Vary: Accept-Encoding
  Connection: close
  Content-Type: text/html

Comment 4

[Vidar Haarr (not reading bugmail)]

Confirming as valid RFE.

Comment 5

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 6

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420