Support for case insensitive locales about routing-filter

[rubyconvict]

Hi, this leads to duplicate content, IMHO - a bad idea. Take this article for example: http://www.hobo-web.co.uk/duplicate-content-problems/

[kennyadsl]

@rubyconvict you are totally right! I didn't considered this aspect. Do you have any other idea about how to implement this? Or do you think it's not doable at all?

[simi]

What's the usecase for this?

[kennyadsl]

@simi users could type website paths using both locale segments:

• website.com/zh-CN
• website.com/zh-cn

The last one (zh-cn), as it is now (or as I think it is 😄), will not be accepted as valid because it's not listed into I18n.available_locales.

We are looking for a valid solution to accept both versions setting the current locale to zh-CN, if possible.

[simi]

Just redirect from website.com/zh-cn/* to zh-CN/*.

[kennyadsl]

Well, redirecting was what I was trying to avoid since zh-CN is not the only possible locale with this issue and, being needed on a multidomain platform on which each domain can have multiple locales, it would require more maintenance work per domain/locale. I was trying to figure out if this can be made dynamic. Thanks anyway!

[kennyadsl]

@simi p.s sorry for not pointing that out in the too simplified usecase I've presented!

[rubyconvict]

301 redirect is the way to go for SEO, if locele is not in case sensitive I18n.available_locales, I would check downcased version against downcased array of locales and redirect based on mapping from downcased match, eg. {"zh-cn" => "zh-CN"}. Indeed, this would be cool opt-in feature for this gem.

[kennyadsl]

@rubyconvict yes, that would be great and solve our usecase. Just wondering if and how is possible to make redirects from inside a routing filter. I can't see anything like that in other provided filters.