On Feb 22, 3:55 pm, Russell Keith-Magee <freakboy3...@gmail.com>
wrote:
> So - what exactly are you proposing that we change in Django?
>
> Looking at your proposal as a purely end-user suggestion: using
> 'hello/*$' means that hello////// will match your URL pattern.
> 'hello/?$' would be a safer match, as it would only match a single
> trailing slash.
>
I was just special-casing the backslash, which is special anyway,
otherwise APPEND_SLASH wouldn't exist.
Moreover, hello and hello/ (and hello/////) _are_ the same URL to
Django, otherwise it wouldn't redirect to the url with the slash
appended. APPEND_SLASH looks more like a hack, so why not treat the
URLs the same from the beginning? This is all I was proposing.
> However, it still wouldn't be a good idea to deploy this pattern. Some
> search engines (Google being a notable and prominent example) penalize
> websites that post identical content on multiple different URLs, as
> this is a common marker of SEO spam. Deploying hello/*? or hello/?$
> means that multiple URLs will serve the same content. Problems with
> trailing slashes notwithstanding, the APPEND_SLASH approach uses a
> redirect, which doesn't attract the same 'Google penalty'.
>
Don't Google folks special-case the trailing slash and assume that
URLs that only differ in the amount of trailing slashes (0 or more)
are the same? Too bad then.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
