205228 - sidebar doesn't change stored URL after receiving 301

Status: NEW

(SeaMonkey :: Sidebar, enhancement)

Description

[Willem Broekema]

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3) Gecko/20030312
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3) Gecko/20030312

If loading a sidebar results in HTTP response code 301, 'Moved Permanently',
then the url of the sidebar is out of date, and should internally be replaced by
the one to which the HTTP header redirects.

So, if the sidebar has initially stored A as url, and A gives 301 -> B, then B
should become the url associated with the sidebar.

Reproducible: Always

Steps to Reproduce:
1. Visit http://wilm.nl/project/zope/sidebar/oud_add and click on 'add Zope
sidebar ... HERE'
2. Click on "Zope" in the sidebar frame: the browser is redirected to the new
sidebar url
3. Click on another sidebar, then on Zope again
Actual Results:  
In step 3, the sidebar is loaded from the old location again (and redirected),
http://wilm.nl/project/zope/sidebar/ , instead of the new location,
http://pastelhorn.com/project/zope/sidebar/ 

Expected Results:  
Mozilla should have loaded the sidebar from the new location instead, because
the 301 HTTP status code should be considered "permanent".

It the associated url gets updated, this is a nice way to update out-of-date
sidebar urls in use.

Comment 1

[Adam Hauner]

Confirming as enhancement.

Comment 2

[Garth Wallace]

Probably related to bug #8648.

Comment 3

[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 4

[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

Comment 5

[Karsten Düsterloh]

Still a valid RFE.