Hi Emilien,
Largely a matter of taste, but my suggestion would be this: If your
URL has other URLs 'under' it (eg, /users/ and /users/john), it should
end with a slash; if not, it should not. This helps with relative
URLs, too - a relative URL from /users to /users/john has to include
the whole fragment ('users/john'), while a relative URL from /users/
only has to include 'john'.
In any case, sending redirects to the 'correct' version is a good
idea, particularly in the direction of adding trailing slashes.
-Nick Johnson
On Thu, Aug 6, 2009 at 11:58 PM, Emilien Klein<[email protected]> wrote:
>
> Hi,
>
> This is a question purely about style. Should the urls of our App
> Engine applications end with a slash or not?
>
> In one of my first applications, I had set up a 301 redirect if you
> queried the page without a trailing slash to the page with the slash.
> Example:
> http://reply.appspot.com/about -> http://reply.appspot.com/about/
>
> Do you think that urls should have a slash at the end or not? And
> whatever's your opinion on this subject, do you think that we should
> redirect the other option to the "real" url (with slash to no slash,
> or no slash to with slash)???
>
> There seems to be different point of view on this subject, so I'd like
> to hear yours!
>
> Cheers,
> Emilien Klein.
> >
>
--
Nick Johnson, Developer Programs Engineer, App Engine
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google App Engine" 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/google-appengine?hl=en
-~----------~----~----~----~------~----~------~--~---
