How to make Vanity URLs case insensitive without using dispatcher? | Community
Skip to main content
vasimakram
vasimakram
Level 4
October 16, 2015
Solved

How to make Vanity URLs case insensitive without using dispatcher?

  • October 16, 2015
  • 3 replies
  • 2989 views

Can any one tell me how to make Vanity URLs case insensitive which are given in a page properties of a page in CQ ?

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by Runal_Trivedi

    well you can write Apache rewrite to convert your URL to all lowercase, Below are some helpful links for handling it on Apache level

    http://www.askapache.com/htaccess/rewrite-uppercase-lowercase.html

    http://serverfault.com/questions/177647/convert-and-redirect-url-in-uppercase-to-lowercase-using-htaccess

    with above approach only drawback is that author needs to make sure that whenever a page is created or vanity URL is defined in AEM it is all in lowercase, else once the request moves from Apache to AEM, it might not be able to identify the node in sling resource resolution process.

    - Runal

    3 replies

    WhoaShekhar
    WhoaShekhar
    Level 10
    October 16, 2015

    Hi there,

    Thanks for reaching out to Adobe Community.

    Please go through the below link and see if it helps:

    https://helpx.adobe.com/experience-manager/kb/vanity-urls.html

    Thanks!

    vasimakram
    vasimakramAuthor
    Level 4
    October 16, 2015

    Hi,

    Thanks for responding, This works for case sensitive. But I want this to work for whatever case I enter. Could you help?

    Runal_Trivedi
    Runal_TrivediAccepted solution
    Level 6
    October 16, 2015

    well you can write Apache rewrite to convert your URL to all lowercase, Below are some helpful links for handling it on Apache level

    http://www.askapache.com/htaccess/rewrite-uppercase-lowercase.html

    http://serverfault.com/questions/177647/convert-and-redirect-url-in-uppercase-to-lowercase-using-htaccess

    with above approach only drawback is that author needs to make sure that whenever a page is created or vanity URL is defined in AEM it is all in lowercase, else once the request moves from Apache to AEM, it might not be able to identify the node in sling resource resolution process.

    - Runal

      Terms & ConditionsAccessibility statement

      Loading footer...