ibolmo wrote: > I had a similar idea today, but pookey made a good point: search > engines discern this practice. > > I think if the alias, wraps the url to a permanent 303 then it would > be fine. >
I'm very torn about this idea.... Duplicate content is bad, we (should) all know that. So, maybe this alias would just do a redirect. Should that be done at the web server level? Starting up PHP just to do a redirect is a huge overhead. But, he're a use case that might show how it could be useful. Imagine 2 routes, @login and @register. When developing my app, login/register is on the same page. Despite this, I know that at some point in the future, I'll want to separate them. Because I've used distinct rules for this, it's easy to change in the future. I consider this a rare enough use case that simply duplicating the rule is sufficient. Infact, the proposed syntax for an alias isn't really much shorter then copying and pasting a rule. Can anyome come up with a good argument for this feature? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
