Created by: Joe Pagan (joepagan@gmail.com) on 2015/03/19 11:45:37 +0000
Votes at time of UserVoice import: 7
I have recently discovered that you can visit the same page at multiple variations of a URL.
For example, these all server the same content: /testimonials, /TESTIMONIALS, /testimoNIals
I would like to request a config setting that would:
- Allow the existing functionality (available at all variations)
- 301 to the intended slug
- 404 if it's not identical to the intended slug or template directory.
Solutions in the mean time:
- This can be semi resolved with a canonical, but, this requires custom code for every site for something that should be native, but, you cannot 404 it.
- At server level you can 301 it, but 404ing is a bit more tricky, afaik this is impossible with apache to server up the Craft 404 Template, and, very time consuming to do this with nginx.
Other issues with doing it at server level:
The Craft admin area relies on it.
Action URLs require capitals.
A link that is not setup on an entry should 404, I feel that the entry is always 100% intended to live on the exact slug I give it in the backend and absolutely nothing else.
Craft is serving my content on multiple variations of a url. Someone could link it with a capital somewhere, google could index it then said website has dupe content issues.
I have recently discovered that you can visit the same page at multiple variations of a URL.
For example, these all server the same content: /testimonials, /TESTIMONIALS, /testimoNIals
I would like to request a config setting that would:
Solutions in the mean time:
Other issues with doing it at server level:
The Craft admin area relies on it.
Action URLs require capitals.
A link that is not setup on an entry should 404, I feel that the entry is always 100% intended to live on the exact slug I give it in the backend and absolutely nothing else.
Craft is serving my content on multiple variations of a url. Someone could link it with a capital somewhere, google could index it then said website has dupe content issues.