On Jul 10, 2008, at 12:11 AM, ibolmo wrote:

>
> I had a similar idea today, but pookey made a good point: search
> engines discern this practice.

Well, that depends. Those documents get their own URL, the alias is  
there only to provide the user with extra "guess-able" URLs. Maybe  
there should be a parameter to specify the HTTP Status code.

>
> I think if the alias, wraps the url to a permanent 303 then it would
> be fine.
>
> Olmo
>
> On Jul 9, 10:28 am, Marijn <[EMAIL PROTECTED]> wrote:
>> Hi everybody,
>>
>> this week I was wondering if symfony is able to create an alias for a
>> routing rule. What I would prefer is something that allows the
>> developer to specify an alias url for a certain module, action and
>> additional parameters that either is redirected or simply  
>> forwarded to
>> a named routing rule from the routing.yml file.
>>
>> E.g.
>>
>> login:
>>   url:      /login/
>>   param:
>>     module: sfGuardAuth
>>     action: signin
>>
>> signin_alias_redirect:
>>   url:      /signin/
>>   alias:    @login
>>   routing:  redirect
>>
>> signin_alias_forward:
>>   url:      /sign-in/
>>   alias:    @login
>>   routing:  forward
>>
>> It seems to me that this would be a behavior that more developers
>> might like. Is there something like this out there in the form of a
>> plugin or should I file a ticket on this? What are your thoughts?
>>
>> Thanks,
>>
>> Marijn
> >


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to