Edgewall Software

Ticket #3718 (new defect)

Opened 20 months ago

Last modified 14 months ago

Trac should use HTTP 301 Moved when milestones get renamed

Reported by: daniel.connor@… Owned by: jonas
Priority: normal Milestone: 1.0
Component: general Version: 0.9.6
Severity: normal Keywords: redirect rename tracobject consider
Cc:

Description

  1. Create a milestone "Example"
  2. Add a ticket to the milestone
  3. Subscribe to the RSS feed.
  4. Edit the milestone, rename to "Changed Milestone"

Expected behaviour: Trac 'knows' a milestone has been renamed, and does a 301 Moved response code. The client application / browser redirects, and the end user doesn't notice anything out of the ordinary

Actual: Trac doesn't do this. milestone:"milestone name" links break, feeds break, and so much more.

Suggested: A simple entry to a 'milestone (previous) names' table would fix this - when a milestone isn't known, the table is checked, and a 301 is sent with an updated location.

Attachments

Change History

Changed 20 months ago by cboos

  • keywords redirect tracobject added

Interesting. This could perhaps be done for Wiki page renaming too.

Changed 14 months ago by cboos

  • keywords rename consider added
  • milestone set to 1.0

OTOH, this would prevent to recreate a milestone which has previously be renamed, using the #4145 method. There would still be the WebAdmin for this, so the features are not incompatible.

Add/Change #3718 (Trac should use HTTP 301 Moved when milestones get renamed)

Author



Change Properties
<Author field>
Action
as new
as The resolution will be set. Next status will be 'closed'
to The owner will change. Next status will be 'new'
The owner will change to anonymous. Next status will be 'assigned'
 
Note: See TracTickets for help on using tickets.