Brett Thomas wrote:
Most of the URLConf examples I run across use a trailing slash on all
URLs: www.example.com/profile/ <http://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 <http://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...
I could be wrong but I understand it as more of a webserver issue than a
Django convention.
From: http://httpd.apache.org/docs/2.2/mod/mod_dir.html
"A "trailing slash" redirect is issued when the server receives a
request for a URL http://servername/foo/dirname where dirname is a
directory. Directories require a trailing slash, so mod_dir issues a
redirect to http://servername/foo/dirname/.";
--
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.
