213128 - Enhancement request: - give option of automatic/interactive/none update of bookmarks when receiving a 302 redirect from a webserver

Status: RESOLVED DUPLICATE of bug 8648

(SeaMonkey :: Bookmarks & History, enhancement)

Description

[Ian Batterbee]

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

It would be a very handy feature for mozilla to be automatically able to update
bookmarks if it gets a 302 'redirect permanently' result from a webserver, or to
at least give the user the option of updating it, and of removing it if it gets
a 404 not found.

For example, I have a number of bookmarks that refer to a site that was moved
some time ago. Eventually redirection support for the old URLs will be removed
from the webserver. Because of the transpararent redirect, the user could easily
be unaware that the URL has changed, and one day their bookmark stops working. I
also have a number of bookmarks that refer to pages that have long since
disappeared that are just a waste of space in my bookmark folder.

The proposed enhancement would apply only when a link was selected from a
bookmark (this would mean we don't have to go searching through all bookmarks to
find if there are any matches for the requested page). If the browser receives a
302/404/whatever http response, it would pop up a box saying the requested web
page has been moved/deleted, and does the user wanted to update their bookmark.
There could be selection boxes for '[ ] update automatically (don't ask)' and '[
] never update'etc ... there would also need to be preference options accessible
through edit/preferences to manage those options and allow the user to set if
they wanted this action to occur for pages that have been [ ]moved, [ ]removed
and so on.

The only problem I can see if that I don't know how the page request code would
be made aware that the request came from a bookmark, and how to link that back
to that individual bookmark, but that's a exercise for the readers :)

Another option would be to have a command on the bookmarks menu along the lines
of 'validate bookmarks', which would then go through all bookmarks and do an
HTTP HEAD command to validate that they still exist, giving the user the option
to automatically remove pages that no longer exist, and of updating pages that
have moved. I'm sure you get the idea.

Both options could be implemented together.



Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

[Charles Fenwick]

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