DrF Reverse Routing

[eluser]drfloob[/eluser]
You're welcome. It's good to have someone to discuss this stuff with :-)

Reverse Routing doesn't attempt to deal with how redirects are handled, just how uri's are translated.

You're right though, a 301 redirect would be necessary if you're changing a well-established url. However, the ways that legacy routes are handled (or not) are probably a lot more personal and varying than this general concept, so I would leave it to the individual developer to decide their own preference.

Off the top of my head, if you want legacy routes to be redirected with a 301, I suppose you could redirect old routes to a "LegacyRoute" controller with some url translation and 301 redirect magic ... or any number of other solutions. The url helper's set_header function goes back to CI v1.4.1, so it's possible to do a 301 redirect up to about 2 years ago, but yeah, v1.6.2 definitely made it more convenient.

Whether anything else breaks in CI version < 1.6.2 is beyond me ;-)