On Jan 28, 11:54 am, Brett Thomas <brettptho...@gmail.com> wrote: > Most of the URLConf examples I run across use a trailing slash on all > URLs:www.example.com/profile/ > > I'm not sure why, but I don't like this. I think it looks nicer > without:www.example.com/profile > > Are there any performance or security reasons to use the trailing slash in > Django? Seems like there could be some quirk with regular expressions that > I'm not thinking of...
If you don't have a trailing slash for something which is an internal node, ie., can have child pages, and you use a relative URL rather than absolute URL, then the relative URL will be resolved incorrectly by the browser. For example, if at '/some/path/' and returned HTML uses 'child.html', then browser will resolve it as: /some/path/child.html if accessed as '/some/path' and returned HTML uses 'child,html', then browser will resolve it as: /some/child.html which isn't want you want. So, you use trailing slash if you want relative URLs in responses. Either way, you should use one of the other and not allow both at the same time. That is '/some/path/' and '/some/path' should not both work. If you do allow both, then search engines will have multiple entries for same resource. Also may stuff up caching systems or at least reduce their efficiency as will keep multiple copies. Graham -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
