On Feb 22, 7:47 pm, Jacob Kaplan-Moss <jacob.kaplanm...@gmail.com>
wrote:
> On Sun, Feb 22, 2009 at 9:37 AM, rihad <ri...@mail.ru> wrote:
> > Unless someone kindly proves me wrong, I really do think trailing
> > slashes in the URL should be optional,
>
> As Russ already said -- did you read his post? -- this is already *up
> to you*. If you want trailing slashes to be optional:
>
> 1. Set APPEND_SLASH to False.
> 2. Write your urlconfs with optional slashes.
> 3. There is no step three.
>
> Django itself makes no assumptions about how you'd like to design your
> URLs. Behavior like APPEND_SLASH and PREPEND_WWW are shortcuts for
> common desires, but both are incredibly easy to disable.
>
Yup, they can be any value, APPEND_SLASH wasn't the main point. At
least djangobook teaches us to end all complete URLs in a slash, which
IMHO should really be optional, so that the regex matches with or
without the trailing slash(es) in the actual URL, _and_ without
incurring the HTTP round-trip through redirection. Just a suggestion,
please don't take it too harshly ;)
> Why don't you back up a step: What are you trying to do that isn't working?
Nothing, really, It was just a design suggestion.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
