Reputation: 651
Let's say that I have a web app that responds to URLs in the format /entities/{entityKey}
. In my access logs, I find people visiting both /entities/KEY1
which is how app URLs are generated, as well as the lower case version of /entities/key1
. Currently key1 will throw a 404 not found error due to route requirements.
My question is, would you:
Upvotes: 0
Views: 135
Reputation: 590
Most users these days expect URLs to be case-insensitive. I would have the app silently handle the conversion in the background. I don't see it being worth the extra request time to issue a redirect.
If SEO is a concern, then you can use the rel="canonical" meta tag to let google/other search engines know which URL you want to appear in search results.
Upvotes: 2