There appears to be a disconnect between the case-sensitivity of URL wildcards and the interface where they are created. For instance, we have a URL wildcard "blog" that redirects to content/view/full/42. If the user enters "Blog" instead of "blog," a page-not-found error results. If you go into the admin URL wildcard interface and try to add "Blog" as an additional wildcard, you are informed that wildcard "blog" already exists and you cannot create the new one. This essentially renders this system incapable of producing case-insensitive aliases.

We know that we can use mod_rewrite to achieve what we intend and we in fact do use mod_rewrite for that. However, we were hoping to be able to allow EZP admins to set up aliases rather than always relying on our server administrator. Is there something we are missing about how to achieve case-insensitive URL redirection aliases in EZP? I have googled around and looked in the EZP documentation and can find little about this but maybe I just haven't found it yet.

Please let us know if this can be fixed or if this feature is unusable for our needs and we have to use mod_rewrite.

Steps to reproduce

1. Create URL wildcard alias "blog" that redirects to About/News/Blog.
2. Browse to http://www.example.org/Blog to confirm that URL alias is case-sensitive, i.e. user gets "page not found" error.
3. Try to create URL wildcard alias "Blog" that redirects to About/News/Blog, receive message stating that the alias already exists.